application op guide
TRANSCRIPT
Application Operations GuideSAP Supplier Relationship Management powered by SAPNetWeaverreg
Target Audience
n System Administratorsn Technology Consultants
PUBLICDocument version 10 ‒ 11212008
Document History
Caution
Before you start the implementation make sure you have the latest version of this document Youcan find the latest version at the following location httpservicesapcominstguides
Installation and Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM Server 70
The following table provides an overview of the most important document changes
Version Date Description
10 11212008 Final Version[Description]
266 PUBLIC 11212008
Table of Contents
Chapter 1 Getting Started 711 About this Guide 712 Important SAP Notes 8
Chapter 2 Overview of SAP Supplier Relationship Management 70 921 Technical System Landscape 9211 ABAP Components 9212 Java Components 10213 Additional Components 1122 Software Component Matrix 1223 Related Documentation 12
Chapter 3 Monitoring of SAP SRM 1531 Alert Monitoring with CCMS 15311 CCMSMonitoring Installation and Setup 16312 Alert Monitoring of Components 163121 SAP NetWeaver 701 Monitoring 163122 Monitoring SAP SRM Server 70 173123 Monitoring of SAP LACWPS 70 1831231 GRMG Availability Monitoring for SAP LACWPS 70 1831232 Activating GRMGMonitoring 1931233 Verifying the GRMG Availability Monitoring 2131234 Troubleshooting GRMG Availability Monitoring 223124 SAP SRMMonitor 253125 Monitoring SAP SRM-MDMCatalog 30 2831251 SAP SRM-MDMCatalog 30 2831252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30 2932 Detailed Monitoring and Tools for Problem and Performance Analysis 30321 Component-Specific Analysis Tools 303211 SAP Supplier Relationship Management (SAP SRM) 70 303212 SAP Live Auction Cockpit Web Presentation Server (LACWPS) 70 393213 SAP SRM-MDMCatalog 30 30322 Scenario Problem Analysis Tools 313221 Interfaces 313222 Data Archiving Monitors 31
11212008 PUBLIC 366
3223 Distributed Statistical Records 313224 Business Packages 32323 Logs and Trace (Component or Scenario-Specific) 32
Chapter 4 Management of SAP SRM 3341 Administration Tools of Software Components 3342 Software Configuration 3343 Starting and Stopping 3444 Backup and Restore 35441 General Remarks 36442 Backup of Individual Components in an SAP SRM Landscape 374421 BampR for Operating System Software and Configuration Data 374422 Database BampR 384423 B amp R for SAP Web Application Server (WebAS) 701 39443 BampR for Individual System Components 394431 SAP Live Auction Cockpit Web Presentation Server (LACWPS) 70 394432 SAP SRM-MDMCatalog 30 39444 BampR for a Complete SAP SRM Landscape 404441 Landscape Shutdown 404442 Offline Backup of the SAP SRM Landscape 404443 Landscape Startup 41445 BampR for an SAP SRM Business Scenario 4145 System Copy 4146 Scheduled and Manual Periodical Tasks 41461 Periodical Tasks for SAP NetWeaver 701 41462 Periodical Tasks for SAP SRM 70 42463 Periodical Tasks for SAP SRM-MDMCatalog 30 42464 Manual Periodical Tasks for SAP SRM 70 4347 Log on and Load Balancing 4348 User Management 43481 Portal User Management 444811 Activating the TPD for User Integration Between SAP SRM Server (SUS) and
SAP Enterprise Portal 444812 SRM Server (SUS) and Portal User Integration 45
Chapter 5 High Availability 47
Chapter 6 Software Change Management 4961 Transport and Change Management 4962 Development Requests and Development Release Management 5063 Support Packages and SAP Notes Implementation 5064 Release and Upgrade Management 51
466 PUBLIC 11212008
65 Template Management 5166 Quality Management and Test Management 51
Chapter 7 Troubleshooting 53
Chapter 8 Appendix 5581 Categories of System Components for Backup and Restore 5582 Related Information 57
Chapter A Reference 59A1 The Main SAP Documentation Types 59
11212008 PUBLIC 566
666 PUBLIC 11212008
1 Getting Started
1 Getting Started
Caution
This guide does not replace the daily operations section that we recommend customers create fortheir specific production operations
11 About this Guide
Designing implementing and running your SAP solution at peak performance 24 hours a day hasnever been more vital for your business success than nowThis guide provides a starting point for managing your SAP solutions and maintaining and runningthem optimally It contains specific information for various tasks and lists the tools that you can useto implement them This guide also provides references to the documentation required for thesetasks so you may need to consult other Guides such as theMaster Guide and SAP LibraryThe following NetWeaver documentation is especially important and must be used in conjunctionwith this SRM Application Operations Guide as the SRM guide covers only SRM-specific topics notgeneral NetWeaver topics
Document Found At
Technical Operations Manual for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
Operations Guide for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations
SAP NetWeaver Security Guide httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide
Solution Life Cycle Management by Key Capability httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability
11212008 PUBLIC 766
1 Getting Started12 Important SAP Notes
12 Important SAP Notes
Caution
Check regularly to see which SAP Notes are available for the Application Operations Guide
SAP Note Number Title
19227 Get the latest saposcol
209834 CCMS agent technology
797147 Wily Introscope Installation for SAP Customers
1126859 End-to-End Diagnostics SP15
866 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 70
2 Overview of SAP Supplier RelationshipManagement 70
SAP Supplier Relationship Management 70 (SAP SRM 70) is delivered to customers as a BusinessSuite Application for procurement and sourcing requirements
21 Technical System Landscape
SAP Supplier Relationship Management 70 (SAP SRM 70) is based on SAP NetWeaver 701 Technologyand consists of various components each of which serve a specific function (as is described in theMaster Guide)For more information on the components and business scenarios please see theMaster Guideat httpservicesapcominstguides Installation and Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 The following diagrams summarize the technical components included in SAP SRM
211 ABAP Components
The ABAP Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n SRM Serverl SRM Server 70
l SRM Plus 70
l SRM Extended Functionality 70
11212008 PUBLIC 966
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
l SRM Extension Plus 70
Figure 1
212 Java Components
The JAVA Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n Live Auction Cockpit
n CCM with SRM MDM Catalog
n TREX
n XI Content
n BI Content
n Portal Content
n Portal Content Supplier
n SRM Java
1066 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
Figure 2
213 Additional Components
The Additional Components of SAP Supplier Relationship Management 70 (SAP SRM 70) include
n SAP Frontend Business Clientl NetWeaver Business Client 710
l SAP GUI for Windows 710 CORE
Figure 3
11212008 PUBLIC 1166
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
Document History
Caution
Before you start the implementation make sure you have the latest version of this document Youcan find the latest version at the following location httpservicesapcominstguides
Installation and Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM Server 70
The following table provides an overview of the most important document changes
Version Date Description
10 11212008 Final Version[Description]
266 PUBLIC 11212008
Table of Contents
Chapter 1 Getting Started 711 About this Guide 712 Important SAP Notes 8
Chapter 2 Overview of SAP Supplier Relationship Management 70 921 Technical System Landscape 9211 ABAP Components 9212 Java Components 10213 Additional Components 1122 Software Component Matrix 1223 Related Documentation 12
Chapter 3 Monitoring of SAP SRM 1531 Alert Monitoring with CCMS 15311 CCMSMonitoring Installation and Setup 16312 Alert Monitoring of Components 163121 SAP NetWeaver 701 Monitoring 163122 Monitoring SAP SRM Server 70 173123 Monitoring of SAP LACWPS 70 1831231 GRMG Availability Monitoring for SAP LACWPS 70 1831232 Activating GRMGMonitoring 1931233 Verifying the GRMG Availability Monitoring 2131234 Troubleshooting GRMG Availability Monitoring 223124 SAP SRMMonitor 253125 Monitoring SAP SRM-MDMCatalog 30 2831251 SAP SRM-MDMCatalog 30 2831252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30 2932 Detailed Monitoring and Tools for Problem and Performance Analysis 30321 Component-Specific Analysis Tools 303211 SAP Supplier Relationship Management (SAP SRM) 70 303212 SAP Live Auction Cockpit Web Presentation Server (LACWPS) 70 393213 SAP SRM-MDMCatalog 30 30322 Scenario Problem Analysis Tools 313221 Interfaces 313222 Data Archiving Monitors 31
11212008 PUBLIC 366
3223 Distributed Statistical Records 313224 Business Packages 32323 Logs and Trace (Component or Scenario-Specific) 32
Chapter 4 Management of SAP SRM 3341 Administration Tools of Software Components 3342 Software Configuration 3343 Starting and Stopping 3444 Backup and Restore 35441 General Remarks 36442 Backup of Individual Components in an SAP SRM Landscape 374421 BampR for Operating System Software and Configuration Data 374422 Database BampR 384423 B amp R for SAP Web Application Server (WebAS) 701 39443 BampR for Individual System Components 394431 SAP Live Auction Cockpit Web Presentation Server (LACWPS) 70 394432 SAP SRM-MDMCatalog 30 39444 BampR for a Complete SAP SRM Landscape 404441 Landscape Shutdown 404442 Offline Backup of the SAP SRM Landscape 404443 Landscape Startup 41445 BampR for an SAP SRM Business Scenario 4145 System Copy 4146 Scheduled and Manual Periodical Tasks 41461 Periodical Tasks for SAP NetWeaver 701 41462 Periodical Tasks for SAP SRM 70 42463 Periodical Tasks for SAP SRM-MDMCatalog 30 42464 Manual Periodical Tasks for SAP SRM 70 4347 Log on and Load Balancing 4348 User Management 43481 Portal User Management 444811 Activating the TPD for User Integration Between SAP SRM Server (SUS) and
SAP Enterprise Portal 444812 SRM Server (SUS) and Portal User Integration 45
Chapter 5 High Availability 47
Chapter 6 Software Change Management 4961 Transport and Change Management 4962 Development Requests and Development Release Management 5063 Support Packages and SAP Notes Implementation 5064 Release and Upgrade Management 51
466 PUBLIC 11212008
65 Template Management 5166 Quality Management and Test Management 51
Chapter 7 Troubleshooting 53
Chapter 8 Appendix 5581 Categories of System Components for Backup and Restore 5582 Related Information 57
Chapter A Reference 59A1 The Main SAP Documentation Types 59
11212008 PUBLIC 566
666 PUBLIC 11212008
1 Getting Started
1 Getting Started
Caution
This guide does not replace the daily operations section that we recommend customers create fortheir specific production operations
11 About this Guide
Designing implementing and running your SAP solution at peak performance 24 hours a day hasnever been more vital for your business success than nowThis guide provides a starting point for managing your SAP solutions and maintaining and runningthem optimally It contains specific information for various tasks and lists the tools that you can useto implement them This guide also provides references to the documentation required for thesetasks so you may need to consult other Guides such as theMaster Guide and SAP LibraryThe following NetWeaver documentation is especially important and must be used in conjunctionwith this SRM Application Operations Guide as the SRM guide covers only SRM-specific topics notgeneral NetWeaver topics
Document Found At
Technical Operations Manual for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
Operations Guide for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations
SAP NetWeaver Security Guide httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide
Solution Life Cycle Management by Key Capability httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability
11212008 PUBLIC 766
1 Getting Started12 Important SAP Notes
12 Important SAP Notes
Caution
Check regularly to see which SAP Notes are available for the Application Operations Guide
SAP Note Number Title
19227 Get the latest saposcol
209834 CCMS agent technology
797147 Wily Introscope Installation for SAP Customers
1126859 End-to-End Diagnostics SP15
866 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 70
2 Overview of SAP Supplier RelationshipManagement 70
SAP Supplier Relationship Management 70 (SAP SRM 70) is delivered to customers as a BusinessSuite Application for procurement and sourcing requirements
21 Technical System Landscape
SAP Supplier Relationship Management 70 (SAP SRM 70) is based on SAP NetWeaver 701 Technologyand consists of various components each of which serve a specific function (as is described in theMaster Guide)For more information on the components and business scenarios please see theMaster Guideat httpservicesapcominstguides Installation and Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 The following diagrams summarize the technical components included in SAP SRM
211 ABAP Components
The ABAP Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n SRM Serverl SRM Server 70
l SRM Plus 70
l SRM Extended Functionality 70
11212008 PUBLIC 966
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
l SRM Extension Plus 70
Figure 1
212 Java Components
The JAVA Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n Live Auction Cockpit
n CCM with SRM MDM Catalog
n TREX
n XI Content
n BI Content
n Portal Content
n Portal Content Supplier
n SRM Java
1066 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
Figure 2
213 Additional Components
The Additional Components of SAP Supplier Relationship Management 70 (SAP SRM 70) include
n SAP Frontend Business Clientl NetWeaver Business Client 710
l SAP GUI for Windows 710 CORE
Figure 3
11212008 PUBLIC 1166
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
Table of Contents
Chapter 1 Getting Started 711 About this Guide 712 Important SAP Notes 8
Chapter 2 Overview of SAP Supplier Relationship Management 70 921 Technical System Landscape 9211 ABAP Components 9212 Java Components 10213 Additional Components 1122 Software Component Matrix 1223 Related Documentation 12
Chapter 3 Monitoring of SAP SRM 1531 Alert Monitoring with CCMS 15311 CCMSMonitoring Installation and Setup 16312 Alert Monitoring of Components 163121 SAP NetWeaver 701 Monitoring 163122 Monitoring SAP SRM Server 70 173123 Monitoring of SAP LACWPS 70 1831231 GRMG Availability Monitoring for SAP LACWPS 70 1831232 Activating GRMGMonitoring 1931233 Verifying the GRMG Availability Monitoring 2131234 Troubleshooting GRMG Availability Monitoring 223124 SAP SRMMonitor 253125 Monitoring SAP SRM-MDMCatalog 30 2831251 SAP SRM-MDMCatalog 30 2831252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30 2932 Detailed Monitoring and Tools for Problem and Performance Analysis 30321 Component-Specific Analysis Tools 303211 SAP Supplier Relationship Management (SAP SRM) 70 303212 SAP Live Auction Cockpit Web Presentation Server (LACWPS) 70 393213 SAP SRM-MDMCatalog 30 30322 Scenario Problem Analysis Tools 313221 Interfaces 313222 Data Archiving Monitors 31
11212008 PUBLIC 366
3223 Distributed Statistical Records 313224 Business Packages 32323 Logs and Trace (Component or Scenario-Specific) 32
Chapter 4 Management of SAP SRM 3341 Administration Tools of Software Components 3342 Software Configuration 3343 Starting and Stopping 3444 Backup and Restore 35441 General Remarks 36442 Backup of Individual Components in an SAP SRM Landscape 374421 BampR for Operating System Software and Configuration Data 374422 Database BampR 384423 B amp R for SAP Web Application Server (WebAS) 701 39443 BampR for Individual System Components 394431 SAP Live Auction Cockpit Web Presentation Server (LACWPS) 70 394432 SAP SRM-MDMCatalog 30 39444 BampR for a Complete SAP SRM Landscape 404441 Landscape Shutdown 404442 Offline Backup of the SAP SRM Landscape 404443 Landscape Startup 41445 BampR for an SAP SRM Business Scenario 4145 System Copy 4146 Scheduled and Manual Periodical Tasks 41461 Periodical Tasks for SAP NetWeaver 701 41462 Periodical Tasks for SAP SRM 70 42463 Periodical Tasks for SAP SRM-MDMCatalog 30 42464 Manual Periodical Tasks for SAP SRM 70 4347 Log on and Load Balancing 4348 User Management 43481 Portal User Management 444811 Activating the TPD for User Integration Between SAP SRM Server (SUS) and
SAP Enterprise Portal 444812 SRM Server (SUS) and Portal User Integration 45
Chapter 5 High Availability 47
Chapter 6 Software Change Management 4961 Transport and Change Management 4962 Development Requests and Development Release Management 5063 Support Packages and SAP Notes Implementation 5064 Release and Upgrade Management 51
466 PUBLIC 11212008
65 Template Management 5166 Quality Management and Test Management 51
Chapter 7 Troubleshooting 53
Chapter 8 Appendix 5581 Categories of System Components for Backup and Restore 5582 Related Information 57
Chapter A Reference 59A1 The Main SAP Documentation Types 59
11212008 PUBLIC 566
666 PUBLIC 11212008
1 Getting Started
1 Getting Started
Caution
This guide does not replace the daily operations section that we recommend customers create fortheir specific production operations
11 About this Guide
Designing implementing and running your SAP solution at peak performance 24 hours a day hasnever been more vital for your business success than nowThis guide provides a starting point for managing your SAP solutions and maintaining and runningthem optimally It contains specific information for various tasks and lists the tools that you can useto implement them This guide also provides references to the documentation required for thesetasks so you may need to consult other Guides such as theMaster Guide and SAP LibraryThe following NetWeaver documentation is especially important and must be used in conjunctionwith this SRM Application Operations Guide as the SRM guide covers only SRM-specific topics notgeneral NetWeaver topics
Document Found At
Technical Operations Manual for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
Operations Guide for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations
SAP NetWeaver Security Guide httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide
Solution Life Cycle Management by Key Capability httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability
11212008 PUBLIC 766
1 Getting Started12 Important SAP Notes
12 Important SAP Notes
Caution
Check regularly to see which SAP Notes are available for the Application Operations Guide
SAP Note Number Title
19227 Get the latest saposcol
209834 CCMS agent technology
797147 Wily Introscope Installation for SAP Customers
1126859 End-to-End Diagnostics SP15
866 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 70
2 Overview of SAP Supplier RelationshipManagement 70
SAP Supplier Relationship Management 70 (SAP SRM 70) is delivered to customers as a BusinessSuite Application for procurement and sourcing requirements
21 Technical System Landscape
SAP Supplier Relationship Management 70 (SAP SRM 70) is based on SAP NetWeaver 701 Technologyand consists of various components each of which serve a specific function (as is described in theMaster Guide)For more information on the components and business scenarios please see theMaster Guideat httpservicesapcominstguides Installation and Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 The following diagrams summarize the technical components included in SAP SRM
211 ABAP Components
The ABAP Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n SRM Serverl SRM Server 70
l SRM Plus 70
l SRM Extended Functionality 70
11212008 PUBLIC 966
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
l SRM Extension Plus 70
Figure 1
212 Java Components
The JAVA Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n Live Auction Cockpit
n CCM with SRM MDM Catalog
n TREX
n XI Content
n BI Content
n Portal Content
n Portal Content Supplier
n SRM Java
1066 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
Figure 2
213 Additional Components
The Additional Components of SAP Supplier Relationship Management 70 (SAP SRM 70) include
n SAP Frontend Business Clientl NetWeaver Business Client 710
l SAP GUI for Windows 710 CORE
Figure 3
11212008 PUBLIC 1166
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3223 Distributed Statistical Records 313224 Business Packages 32323 Logs and Trace (Component or Scenario-Specific) 32
Chapter 4 Management of SAP SRM 3341 Administration Tools of Software Components 3342 Software Configuration 3343 Starting and Stopping 3444 Backup and Restore 35441 General Remarks 36442 Backup of Individual Components in an SAP SRM Landscape 374421 BampR for Operating System Software and Configuration Data 374422 Database BampR 384423 B amp R for SAP Web Application Server (WebAS) 701 39443 BampR for Individual System Components 394431 SAP Live Auction Cockpit Web Presentation Server (LACWPS) 70 394432 SAP SRM-MDMCatalog 30 39444 BampR for a Complete SAP SRM Landscape 404441 Landscape Shutdown 404442 Offline Backup of the SAP SRM Landscape 404443 Landscape Startup 41445 BampR for an SAP SRM Business Scenario 4145 System Copy 4146 Scheduled and Manual Periodical Tasks 41461 Periodical Tasks for SAP NetWeaver 701 41462 Periodical Tasks for SAP SRM 70 42463 Periodical Tasks for SAP SRM-MDMCatalog 30 42464 Manual Periodical Tasks for SAP SRM 70 4347 Log on and Load Balancing 4348 User Management 43481 Portal User Management 444811 Activating the TPD for User Integration Between SAP SRM Server (SUS) and
SAP Enterprise Portal 444812 SRM Server (SUS) and Portal User Integration 45
Chapter 5 High Availability 47
Chapter 6 Software Change Management 4961 Transport and Change Management 4962 Development Requests and Development Release Management 5063 Support Packages and SAP Notes Implementation 5064 Release and Upgrade Management 51
466 PUBLIC 11212008
65 Template Management 5166 Quality Management and Test Management 51
Chapter 7 Troubleshooting 53
Chapter 8 Appendix 5581 Categories of System Components for Backup and Restore 5582 Related Information 57
Chapter A Reference 59A1 The Main SAP Documentation Types 59
11212008 PUBLIC 566
666 PUBLIC 11212008
1 Getting Started
1 Getting Started
Caution
This guide does not replace the daily operations section that we recommend customers create fortheir specific production operations
11 About this Guide
Designing implementing and running your SAP solution at peak performance 24 hours a day hasnever been more vital for your business success than nowThis guide provides a starting point for managing your SAP solutions and maintaining and runningthem optimally It contains specific information for various tasks and lists the tools that you can useto implement them This guide also provides references to the documentation required for thesetasks so you may need to consult other Guides such as theMaster Guide and SAP LibraryThe following NetWeaver documentation is especially important and must be used in conjunctionwith this SRM Application Operations Guide as the SRM guide covers only SRM-specific topics notgeneral NetWeaver topics
Document Found At
Technical Operations Manual for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
Operations Guide for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations
SAP NetWeaver Security Guide httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide
Solution Life Cycle Management by Key Capability httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability
11212008 PUBLIC 766
1 Getting Started12 Important SAP Notes
12 Important SAP Notes
Caution
Check regularly to see which SAP Notes are available for the Application Operations Guide
SAP Note Number Title
19227 Get the latest saposcol
209834 CCMS agent technology
797147 Wily Introscope Installation for SAP Customers
1126859 End-to-End Diagnostics SP15
866 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 70
2 Overview of SAP Supplier RelationshipManagement 70
SAP Supplier Relationship Management 70 (SAP SRM 70) is delivered to customers as a BusinessSuite Application for procurement and sourcing requirements
21 Technical System Landscape
SAP Supplier Relationship Management 70 (SAP SRM 70) is based on SAP NetWeaver 701 Technologyand consists of various components each of which serve a specific function (as is described in theMaster Guide)For more information on the components and business scenarios please see theMaster Guideat httpservicesapcominstguides Installation and Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 The following diagrams summarize the technical components included in SAP SRM
211 ABAP Components
The ABAP Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n SRM Serverl SRM Server 70
l SRM Plus 70
l SRM Extended Functionality 70
11212008 PUBLIC 966
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
l SRM Extension Plus 70
Figure 1
212 Java Components
The JAVA Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n Live Auction Cockpit
n CCM with SRM MDM Catalog
n TREX
n XI Content
n BI Content
n Portal Content
n Portal Content Supplier
n SRM Java
1066 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
Figure 2
213 Additional Components
The Additional Components of SAP Supplier Relationship Management 70 (SAP SRM 70) include
n SAP Frontend Business Clientl NetWeaver Business Client 710
l SAP GUI for Windows 710 CORE
Figure 3
11212008 PUBLIC 1166
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
65 Template Management 5166 Quality Management and Test Management 51
Chapter 7 Troubleshooting 53
Chapter 8 Appendix 5581 Categories of System Components for Backup and Restore 5582 Related Information 57
Chapter A Reference 59A1 The Main SAP Documentation Types 59
11212008 PUBLIC 566
666 PUBLIC 11212008
1 Getting Started
1 Getting Started
Caution
This guide does not replace the daily operations section that we recommend customers create fortheir specific production operations
11 About this Guide
Designing implementing and running your SAP solution at peak performance 24 hours a day hasnever been more vital for your business success than nowThis guide provides a starting point for managing your SAP solutions and maintaining and runningthem optimally It contains specific information for various tasks and lists the tools that you can useto implement them This guide also provides references to the documentation required for thesetasks so you may need to consult other Guides such as theMaster Guide and SAP LibraryThe following NetWeaver documentation is especially important and must be used in conjunctionwith this SRM Application Operations Guide as the SRM guide covers only SRM-specific topics notgeneral NetWeaver topics
Document Found At
Technical Operations Manual for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
Operations Guide for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations
SAP NetWeaver Security Guide httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide
Solution Life Cycle Management by Key Capability httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability
11212008 PUBLIC 766
1 Getting Started12 Important SAP Notes
12 Important SAP Notes
Caution
Check regularly to see which SAP Notes are available for the Application Operations Guide
SAP Note Number Title
19227 Get the latest saposcol
209834 CCMS agent technology
797147 Wily Introscope Installation for SAP Customers
1126859 End-to-End Diagnostics SP15
866 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 70
2 Overview of SAP Supplier RelationshipManagement 70
SAP Supplier Relationship Management 70 (SAP SRM 70) is delivered to customers as a BusinessSuite Application for procurement and sourcing requirements
21 Technical System Landscape
SAP Supplier Relationship Management 70 (SAP SRM 70) is based on SAP NetWeaver 701 Technologyand consists of various components each of which serve a specific function (as is described in theMaster Guide)For more information on the components and business scenarios please see theMaster Guideat httpservicesapcominstguides Installation and Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 The following diagrams summarize the technical components included in SAP SRM
211 ABAP Components
The ABAP Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n SRM Serverl SRM Server 70
l SRM Plus 70
l SRM Extended Functionality 70
11212008 PUBLIC 966
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
l SRM Extension Plus 70
Figure 1
212 Java Components
The JAVA Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n Live Auction Cockpit
n CCM with SRM MDM Catalog
n TREX
n XI Content
n BI Content
n Portal Content
n Portal Content Supplier
n SRM Java
1066 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
Figure 2
213 Additional Components
The Additional Components of SAP Supplier Relationship Management 70 (SAP SRM 70) include
n SAP Frontend Business Clientl NetWeaver Business Client 710
l SAP GUI for Windows 710 CORE
Figure 3
11212008 PUBLIC 1166
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
666 PUBLIC 11212008
1 Getting Started
1 Getting Started
Caution
This guide does not replace the daily operations section that we recommend customers create fortheir specific production operations
11 About this Guide
Designing implementing and running your SAP solution at peak performance 24 hours a day hasnever been more vital for your business success than nowThis guide provides a starting point for managing your SAP solutions and maintaining and runningthem optimally It contains specific information for various tasks and lists the tools that you can useto implement them This guide also provides references to the documentation required for thesetasks so you may need to consult other Guides such as theMaster Guide and SAP LibraryThe following NetWeaver documentation is especially important and must be used in conjunctionwith this SRM Application Operations Guide as the SRM guide covers only SRM-specific topics notgeneral NetWeaver topics
Document Found At
Technical Operations Manual for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
Operations Guide for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations
SAP NetWeaver Security Guide httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide
Solution Life Cycle Management by Key Capability httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability
11212008 PUBLIC 766
1 Getting Started12 Important SAP Notes
12 Important SAP Notes
Caution
Check regularly to see which SAP Notes are available for the Application Operations Guide
SAP Note Number Title
19227 Get the latest saposcol
209834 CCMS agent technology
797147 Wily Introscope Installation for SAP Customers
1126859 End-to-End Diagnostics SP15
866 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 70
2 Overview of SAP Supplier RelationshipManagement 70
SAP Supplier Relationship Management 70 (SAP SRM 70) is delivered to customers as a BusinessSuite Application for procurement and sourcing requirements
21 Technical System Landscape
SAP Supplier Relationship Management 70 (SAP SRM 70) is based on SAP NetWeaver 701 Technologyand consists of various components each of which serve a specific function (as is described in theMaster Guide)For more information on the components and business scenarios please see theMaster Guideat httpservicesapcominstguides Installation and Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 The following diagrams summarize the technical components included in SAP SRM
211 ABAP Components
The ABAP Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n SRM Serverl SRM Server 70
l SRM Plus 70
l SRM Extended Functionality 70
11212008 PUBLIC 966
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
l SRM Extension Plus 70
Figure 1
212 Java Components
The JAVA Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n Live Auction Cockpit
n CCM with SRM MDM Catalog
n TREX
n XI Content
n BI Content
n Portal Content
n Portal Content Supplier
n SRM Java
1066 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
Figure 2
213 Additional Components
The Additional Components of SAP Supplier Relationship Management 70 (SAP SRM 70) include
n SAP Frontend Business Clientl NetWeaver Business Client 710
l SAP GUI for Windows 710 CORE
Figure 3
11212008 PUBLIC 1166
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
1 Getting Started
1 Getting Started
Caution
This guide does not replace the daily operations section that we recommend customers create fortheir specific production operations
11 About this Guide
Designing implementing and running your SAP solution at peak performance 24 hours a day hasnever been more vital for your business success than nowThis guide provides a starting point for managing your SAP solutions and maintaining and runningthem optimally It contains specific information for various tasks and lists the tools that you can useto implement them This guide also provides references to the documentation required for thesetasks so you may need to consult other Guides such as theMaster Guide and SAP LibraryThe following NetWeaver documentation is especially important and must be used in conjunctionwith this SRM Application Operations Guide as the SRM guide covers only SRM-specific topics notgeneral NetWeaver topics
Document Found At
Technical Operations Manual for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
Operations Guide for SAP NetWeaver httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations
SAP NetWeaver Security Guide httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide
Solution Life Cycle Management by Key Capability httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability
11212008 PUBLIC 766
1 Getting Started12 Important SAP Notes
12 Important SAP Notes
Caution
Check regularly to see which SAP Notes are available for the Application Operations Guide
SAP Note Number Title
19227 Get the latest saposcol
209834 CCMS agent technology
797147 Wily Introscope Installation for SAP Customers
1126859 End-to-End Diagnostics SP15
866 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 70
2 Overview of SAP Supplier RelationshipManagement 70
SAP Supplier Relationship Management 70 (SAP SRM 70) is delivered to customers as a BusinessSuite Application for procurement and sourcing requirements
21 Technical System Landscape
SAP Supplier Relationship Management 70 (SAP SRM 70) is based on SAP NetWeaver 701 Technologyand consists of various components each of which serve a specific function (as is described in theMaster Guide)For more information on the components and business scenarios please see theMaster Guideat httpservicesapcominstguides Installation and Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 The following diagrams summarize the technical components included in SAP SRM
211 ABAP Components
The ABAP Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n SRM Serverl SRM Server 70
l SRM Plus 70
l SRM Extended Functionality 70
11212008 PUBLIC 966
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
l SRM Extension Plus 70
Figure 1
212 Java Components
The JAVA Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n Live Auction Cockpit
n CCM with SRM MDM Catalog
n TREX
n XI Content
n BI Content
n Portal Content
n Portal Content Supplier
n SRM Java
1066 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
Figure 2
213 Additional Components
The Additional Components of SAP Supplier Relationship Management 70 (SAP SRM 70) include
n SAP Frontend Business Clientl NetWeaver Business Client 710
l SAP GUI for Windows 710 CORE
Figure 3
11212008 PUBLIC 1166
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
1 Getting Started12 Important SAP Notes
12 Important SAP Notes
Caution
Check regularly to see which SAP Notes are available for the Application Operations Guide
SAP Note Number Title
19227 Get the latest saposcol
209834 CCMS agent technology
797147 Wily Introscope Installation for SAP Customers
1126859 End-to-End Diagnostics SP15
866 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 70
2 Overview of SAP Supplier RelationshipManagement 70
SAP Supplier Relationship Management 70 (SAP SRM 70) is delivered to customers as a BusinessSuite Application for procurement and sourcing requirements
21 Technical System Landscape
SAP Supplier Relationship Management 70 (SAP SRM 70) is based on SAP NetWeaver 701 Technologyand consists of various components each of which serve a specific function (as is described in theMaster Guide)For more information on the components and business scenarios please see theMaster Guideat httpservicesapcominstguides Installation and Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 The following diagrams summarize the technical components included in SAP SRM
211 ABAP Components
The ABAP Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n SRM Serverl SRM Server 70
l SRM Plus 70
l SRM Extended Functionality 70
11212008 PUBLIC 966
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
l SRM Extension Plus 70
Figure 1
212 Java Components
The JAVA Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n Live Auction Cockpit
n CCM with SRM MDM Catalog
n TREX
n XI Content
n BI Content
n Portal Content
n Portal Content Supplier
n SRM Java
1066 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
Figure 2
213 Additional Components
The Additional Components of SAP Supplier Relationship Management 70 (SAP SRM 70) include
n SAP Frontend Business Clientl NetWeaver Business Client 710
l SAP GUI for Windows 710 CORE
Figure 3
11212008 PUBLIC 1166
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
2 Overview of SAP Supplier Relationship Management 70
2 Overview of SAP Supplier RelationshipManagement 70
SAP Supplier Relationship Management 70 (SAP SRM 70) is delivered to customers as a BusinessSuite Application for procurement and sourcing requirements
21 Technical System Landscape
SAP Supplier Relationship Management 70 (SAP SRM 70) is based on SAP NetWeaver 701 Technologyand consists of various components each of which serve a specific function (as is described in theMaster Guide)For more information on the components and business scenarios please see theMaster Guideat httpservicesapcominstguides Installation and Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 The following diagrams summarize the technical components included in SAP SRM
211 ABAP Components
The ABAP Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n SRM Serverl SRM Server 70
l SRM Plus 70
l SRM Extended Functionality 70
11212008 PUBLIC 966
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
l SRM Extension Plus 70
Figure 1
212 Java Components
The JAVA Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n Live Auction Cockpit
n CCM with SRM MDM Catalog
n TREX
n XI Content
n BI Content
n Portal Content
n Portal Content Supplier
n SRM Java
1066 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
Figure 2
213 Additional Components
The Additional Components of SAP Supplier Relationship Management 70 (SAP SRM 70) include
n SAP Frontend Business Clientl NetWeaver Business Client 710
l SAP GUI for Windows 710 CORE
Figure 3
11212008 PUBLIC 1166
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
l SRM Extension Plus 70
Figure 1
212 Java Components
The JAVA Components of SAP Supplier Relationship Management 70 (SAP SRM) include
n Live Auction Cockpit
n CCM with SRM MDM Catalog
n TREX
n XI Content
n BI Content
n Portal Content
n Portal Content Supplier
n SRM Java
1066 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
Figure 2
213 Additional Components
The Additional Components of SAP Supplier Relationship Management 70 (SAP SRM 70) include
n SAP Frontend Business Clientl NetWeaver Business Client 710
l SAP GUI for Windows 710 CORE
Figure 3
11212008 PUBLIC 1166
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
2 Overview of SAP Supplier Relationship Management 7021 Technical System Landscape
Figure 2
213 Additional Components
The Additional Components of SAP Supplier Relationship Management 70 (SAP SRM 70) include
n SAP Frontend Business Clientl NetWeaver Business Client 710
l SAP GUI for Windows 710 CORE
Figure 3
11212008 PUBLIC 1166
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
2 Overview of SAP Supplier Relationship Management 7022 Software Component Matrix
22 Software Component Matrix
For an overview of SAP SRMbusiness scenarios and their associated software units in both ContinuousInnovation and Easy Adoption see the Software Component Matrix for SAP SRM 70 on the SAPService Marketplace at httpservicesapcomsrm-inst SAP SRM SAP SRM Server 70
Note
The Continuous Innovation functions for SAP SRM 70 with some exceptions require the use of SAPNetWeaver 701 The Easy Adoption functions require SAP NetWeaver 70
For the latest component version and patch level requirements see SAP Service Marketplace athttpservicesapcomsp-stacks SAP SRM 70 and the Release Information Note which is
available for each Support Package stack (SAP Note number is listed on the page)
Note
This Master Guide provides just one way to implement each business scenario For other ways toimplement business scenarios see the Scenario amp Process Component list in SAP Service Marketplaceat httpservicesapcomscl The Scenario amp Process Component list helps you to findimplementation alternatives for SAP solutions business scenarios and processes It shows you whichapplication components are needed to implement a business scenario or process
The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 70 package can be found at SAP Service Marketplace athttpservicesapcominstguides SAP Business Suite Applications SAP SRM SAP SRM 70
Note
For each component listed in the Software Component Matrix there are software requirements thatare not explicitly mentioned in this documentation Component-specific software requirements aredocumented for a component in its installation guide All related implementation guides are listedin 6 References [external document]
You require SAP NetWeaver 70reg TREX in the following cases
n When you use the contract management application to search for information such as suppliertexts internal notes and attachments
n When you want to use the metadata search functionality or use BI accelerator within Analytics
23 Related Documentation
The following table lists where you can find more information about the technical system landscape
1266 PUBLIC 11212008
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
2 Overview of SAP Supplier Relationship Management 7023 Related Documentation
Topic GuideTool Location on SAP Service MarketplaceSAP Help Portal
SAP SRM 70 Master Guide httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite ApplicationsSAP SRM SAP SRM Server 70
Sizing Quick Sizer Tool httpservicesapcomsizing SAPNetWeaver SAP NetWeaver in Detail SolutionLife-Cycle Management Hardware Sizing Quick SizerTool
Technical Configuration TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Scalability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
High Availability TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
Security TechnicalInfrastructureGuide
httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation ampImplementation Documentation Center InstallationTechnical Infrastructure Guide
11212008 PUBLIC 1366
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
This page is left blank for documentsthat are printed on both sides
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions The aimof this section is to provide information and documentation required to configure the ComputingCenter Management System (CCMS) and create a user-defined SAP SRMmonitor set reflecting acustomer-specific SAP SRM system landscapeFormore information on the underlying technology see the SAP NetWeaver Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Technical Operations ManualAs SAP SRM 70 is powered by SAP NetWeaver 701 Including Enhancement Package 1 we recommendthat you set up the Monitoring Infrastructure as described in theMonitoring Setup Guide for SAP NetWeaver(MSG) at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Operations Monitoring The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all theinformation relevant to monitoring the SAP NetWeaver components used in SAP SRM 70 Proficientknowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up andmanage the user-defined SRMmonitors recommended within this guide
31 Alert Monitoring with CCMS
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP systemenvironment SAP SRM provides you with the infrastructure and recommendations on how to set upyour alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possibleFor more information see the Monitoring Setup Guide for SAP NetWeaver (MSG) athttphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 System Administration
Operations Monitoring To configure alert monitoring with CCMS for SAP SRM 70 you must set up a Central MonitoringSystem (CEN) and connect all SAP SRM 70 components to this CEN system For a list of thesecomponents and the business scenarios for which they are relevant see section 22ScenarioComponentMatrix [external document]You can access the SRM Server Monitoring templates called SAP (CEN) EnterpriseBuyer Monitorsusing transaction RZ20 (see section 3124 SAP SRMMonitor [page 25] for full details)For more information see the SRM Master Guide on the SAP Service Marketplace athttpservicesapcominstguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 70
11212008 PUBLIC 1566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Since SAP SRM 70 utilizes the complete SAP NetWeaver 70 Including Enhancement Package 1 stackyou have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM componentsfirst In addition to this you can define special SAP SRMmonitors in the CEN systemrsquos CCMS
311 CCMS Monitoring Installation and Setup
To enable the auto-alert mechanism of CCMS see SAP Note 617547
Recommendation
SAP recommends the usage of SAP NetWeaver 70 including enhancement package 1 for Central Monitoring
312 Alert Monitoring of Components
One approach for monitoring an SAP SRM landscape is to monitor each component separately in theCEN system The other approach is to monitor across components based on a business scenarioThis section gives you an overview of how each SAP SRM component could be monitored usingCCMS Which components need to be monitored depends on the SAP SRM scenario(s) implementedFor more information see section 22 ScenarioComponent Matrix [external document]
Note
This monitoring set for SAP SRM 70 includes component-related monitors such as for SAP SRM 70and Live Auction Cockpit 70 (LACWPS 70) These monitors are not delivered by SAP but can becreated in the CEN system All Monitoring Tree Elements (MTE) used for these monitors are basedon the default monitoring templates delivered by SAPFor information on editing or creating monitors and monitor sets see the SAP NetWeaverMonitoring Setup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Operations Monitoring
3121 SAP NetWeaver 701 Monitoring
SAP NetWeaver 701 is the integration and application platform for SAP SRM 70 therefore thefollowing SAP NetWeaver components must be integrated into the monitoring infrastructure
n SAP Web Application Server (ABAP) 701 [for SAP SRM 70]n SAP Web Application Server (Java) 701 [for SAP LACWPS 70]n SAP NetWeaver Usage Type Process Integration (PI)n SAP NetWeaver Enterprise Portal 701n SAP NetWeaver Business Intelligence 701 (SAP NetWeaver BI)
1666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n For more information and detailed procedures please see the SAP NetWeaver Monitoring SetupGuide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including EnhancementPackage 1 System Administration Operations Monitoring and SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Technical Operations Manual
3122 Monitoring SAP SRM Server 70
The main component in your SAP SRM Solution is the SAP SRM 70 It is based on SAP WebApplication Server (ABAP) 701 For more information please see the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SAP SRM Server 70 is connected to the CEN and registered as a remote systemn The SAPCCM4X agent is registered and running for each SAP SRM Server 70 instance
What to MonitorYour SAP SRM Server 70 is running on SAP Web Application Server (ABAP) 701 ‒ which means theprimary points of failure are within the technical infrastructure
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM Server 70 monitor2 On the top level create a virtual node for each of the following areasn Back-end Monitoringn Database
n Operating Systemn System Configurationn Log File Monitoring
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
R3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMServer_Systemsgt
Dialogue Response Time Virtual
R3System ltSRMServer_SystemsgtRule
MTEClass R3DialogResponseTime
11212008 PUBLIC 1766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
Network Time Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass R3UsersLoggedIn
Database Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
Operating System Virtual
R3System ltSRMServer_SystemsgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltSRMSERVER_SYSTEMSgt
Dialog Response Time Virtual
R3System ltSRMSERVER_SYSTEMSgt
MoniSegment ltANYgt
CCMS_GET_MONITORING_CON-TEXT_NAMES
Rule
MoniContext System Configuration
Log File Monitoring Virtual
R3System ltSRMSERVER_SYSTEMSgtCCMS_GET_MTE_BY_CLASS Rule
MTEClass CcmsFileMonitoring no such MTEclass exists needs to be changed tofilesystemMO
3123 Monitoring of SAP LACWPS 70
31231 GRMG Availability Monitoring for SAP LACWPS 70
Note
LACWPS 70 is Java applet front end for users with application business and database management inSAP SRM Server
1866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
LACWPS 70 uses SAP SRM Server for data persistence and business logic the MTE Auction (see section3124 SAP SRMMonitor [page 25]) takes care of the monitoring of LACWPS 70 application-specificmonitoringThe following information is for setting GRMG heartbeat monitoringThe Live Auction Cockpit runs on SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcomnw70 SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
31232 Activating GRMG Monitoring
1 Obtain the XML format customizing files for the GRMGmonitoring scenarios of Live AuctionCockpitA GRMG customizing file tells the central monitoring system to run a particular GRMGavailability monitoring scenario ‒ that is to monitor the availability and condition of a particularcomponentThe GRMG customizing file is named la_grmgxml for Live Auction Cockpit and it can be foundin ltINSTDIRgtusrsapltsystem namegtSYSglobalsrmlamonitoring
2 To adjust the customizing files you need to edit the la_grmgxml file using an XML editor or anyplain text editor Change the URL specified in the ltscenstarturlgt element of the customizing fileto the correct hostname and port of your installation
Example
If your installation uses hostname yourhostname on port 8080 then the value in between theltscenstarturlgt and ltscenstarturlgt tags should beltscenstarturlgthttpyourhostname8080srmheatBeatltscenstarturlgt
Note
Each instance of Live Auction Cockpit that is to be monitored is considered a scenario and needsto be executed by the GRMG frameworkTo monitor more than one instance of Live Auction Cockpit you need to specify each of thescenarios in the XML customizing file For more information see section Adding Scenarios tothe XML Customizing File (below)
3 Upload the customizing file into the central monitoring system
11212008 PUBLIC 1966
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
a) Log on to the monitoring system as a user with administrator rightsMake sure that you log on to the central application server This is the server which offers theenqueue service You can determine which server is your central server with transaction SM51or with transaction RZ03
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbarc) Click Upload a GRMG Scenario
A file-selection dialog box is displayedd) Navigate to the directory in which the customizing file is located and select the filee) Click Open to upload the fileIn the first production release of this transaction no confirmation message is presented Formore information on verifying GRMG settings see Verifying the GRMG Availability Monitoring(below)
4 After you have uploaded all of the customizing files start the availability monitoring
Caution
Be sure that you are logged on to the central application server of the monitoring system beforecarrying out this step The central server is the one that offers the enqueue service You candetermine which server this is in transaction SM51 or transaction RZ03
To start the GRMG availability monitoring click Start all scenarios in transaction GRMG
ResultThe function displays no confirmation message that the availability monitoring has started Formore information on verifying GRMG settings see section 31233 Verifying the GRMG AvailabilityMonitoring [page 21]Once you start GRMGmonitoring the monitoring scenarios which you installed run automaticallyThe CCMS monitoring architecture repeats each GRMG availability monitoring scenarioautomatically every ten minutes by default
Adding Scenarios to the XML Customizing File
1 Copy everything in between the tags (including the tags themselves) ltscenariogt andltscenariogt
2 Paste them below the last ltscenariogt tag3 Repeat this step for each additional instance you wish to monitor4 Modify the values in between ltscenversiongt and ltscenversiongt and ltsceninstgt and
ltsceninstgt so that they are unique for each instance
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value byone for each additional instance (002 003 and so forth)
2066 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
5 Change the URL specified between the ltscenstarturlgt and ltscenstarturlgt tags to the correctand fully qualified hostname and port for this particular scenario
31233 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution StatusThis section describes how to verify that GRMG availability monitoring is running correctly and alsodescribes procedures for analyzing problemsGRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availabilitymonitoring scenario successfully
1 Log on to the monitoring system as a user with administrator rights2 Start transaction RZ20
The transaction presents the list of standard monitor collections in your system3 Expand the monitor collection named SAP CCMS Technical Expert Monitors
The list of monitors in this collection is displayed4 Double-click on the monitor named All Monitoring Contexts
The monitoring tree that reports the status of the monitoring architecture is displayed5 Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element ltscendescgt in the XML customizing file)You should now see a further subtree with the nameWeb Server of SRM Live Auction Scenario
6 Expand theWeb Server of SRM Live Auction Scenario node to open the subtreeThe following screen shot depicts an example of what you can expect to see
Figure 4
11212008 PUBLIC 2166
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
ResultIf theWeb Server of SRM Live Auction Scenario subtree is present and is green then all GRMGmonitoringscenarios are running correctly the GRMG application was contacted and returned a valid answerAs the Heartbeat message indicates you can view the availability data in the normal scenario subtreeunder the full name of the scenarioIf theWeb Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches arered (red alert) or white (monitoring inactive) then an error occurred For more information seesection 31234 Troubleshooting GRMG Availability Monitoring [page 22]
31234 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found
If you were unable to verify the GRMG availability monitoring as described in secion 31233 Verifyingthe GRMG Availability Monitoring [page 21] then one of the following is most likely the cause
n The GRMG availability monitoring was not started on the central application server of yourSAP system1 Check for other MoniInfra_ltserver namegt subtrees in the CCMS Selfmonitoring monitor2 Delete any such trees3 Start GRMGmonitoring on the central application server
n None of the GRMG customizing files that you uploaded could be correctly processed1 Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of eachmonitoring scenario that you uploaded
l TheURLused 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 containcomplete or valid XML customizing data for GRMG
2266 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
2 Download the newest customizing files from the SAP Service Marketplace at the Internetaddress servicesapcommonitoring
Caution
Do not attempt to correct customizing directly in the customizing tables Instead correct theproblems by editing the customizing XML file and uploading the file again
GRMG_SelfMonitoring Subtree Found with Errors
If you were able to find the GRMG_SelfMonitoring subtree click on the subtrees to open them anddisplay the execution status of each scenarioA scenario error means that the monitoring architecture was unable to run the scenario Possiblereasons include
n The host specified in the scenario URL may have been unreachablen No answer was received
n An invalid answer was received
If a scenario error has occurred then the scenario error tree looks similar to the following
Figure 5
In this example an HTTP communication failure occurred This means that the HTTP POST duringthe GRMGmonitoring request could not be completed successfully The most likely cause is thatthe HTTP server does not exist or was not running The Heartbeat node includes the error messagesreturned by the monitoring architecture as it tried to run the scenarioWhenever a scenario error occurs only the scenario error subtree is created or updatedmdash not thenormal monitoring subtree mdash to allow the monitor to distinguish between failure to execute ascenario which may have many causes and the non-availability of the monitored components Ascenario failure does not necessarily mean that the monitored components are unavailable
11212008 PUBLIC 2366
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you havedefined) even if the scenario execution ends in a scenario errorPossible scenario error messages and the most likely causes
GRMG Scenario Error Message Cause
Reason for HTTP POST failuren HTTP communication failuren Connect failedn Time-out occurred
1 The URL specified in the scenario customizingpoints to a non-existent host or portCheck that the URL is valid
2 The HTTP server specified in the URL is notrunningStart the HTTP server if it is not running If theGRMG application runs on the same server as themonitored components then this error messagealso means that the tested components are notavailable
Reason for HTTP POST failuren TCPIP error occurredn Data error occurred
Your installation is having problems with the networkconfiguration or with network operation
Reason for HTTP POST failuren Internal error occurred
There is a problem with the HTTP service in the SAPsystem you are using for monitoring Check on thestatus of this service with transaction SMICM
Reason for HTTP POST failuren System failure occurred
There is a problem with the HTTP server specified inthe scenario URL
Reason for HTTP POST failuren Argument not foundn Plug-in not activel Internal errorl HTTP invalid state
There is a problem with the HTTP client functionin the SAP system you are using for monitoringCheck on the status of your HTTP operations withtransaction SMICM
Reason for HTTP POST failuren Destination not foundn Not authorized to use HTTP destination
You are using an RFC destination of type HTTPinstead of specifying a URL directly in scenariocustomizingThe destination has either not been defined or thereis a destination use authorization problem
Reason for scenario failuren ltno error messagegt
This scenario error often occurs when an HTMLresponse rather than an XML response has beenreturned from the server specified in the scenarioURL In this case the XML parse engine may notreturn specific errors that can be output in thescenario error messageTypically such a scenario error means that theGRMG application targeted in the scenario URL isnot installed at the target hostThe web server may return an HTML page with acode 404 (page not found) message or may returnsome other non-XML response which confuses theXML parser
2466 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
GRMG Scenario Error Message Cause
You should check that the GRMG application isinstalled and runs correctly at the target host
Reason for scenario failuren No response for any component in requestn ltno error messagegt
This error message may occur if a GRMG applicationresponds without reporting the status of any of thecomponents specified in the GRMG monitoringrequestCheck that the components specified in the GRMGcustomizing file match those checked by the GRMGapplicationYou can also compare the GRMG request andresponse directly by switching on HTTP tracing briefly(level 3) in transaction SMICM on the central serverof your monitoring system
Reason for scenario failuren ltAny message relating to invalid XML formatgtn ltno error messagegt
A formal DTD error such as unbalanced tagsoccurred in the responseYou can view the response directly by switching onHTTP tracing briefly (level 3) in transaction SMICMon the central server of your monitoring system
Reason for scenario failuren Any message having to do with the CCMS
monitoring architecture such as- Invalid TID- Wrong segment
There is a problem in the CCMS monitoringarchitectureCheck the alerts elsewhere in the CCMSSelfmonitoring monitor for possible causes Be sureas well that you have started GRMGmonitoring onlyon the central server of the SAP system that you areusing for monitoring
3124 SAP SRM Monitor
Note
In earlier releases SAP SRM used to be known as SAP Enterprise Buyer This is still reflected in thename of the monitor tool which is called SAP EnterpriseBuyer Monitors
To reduce administrative tasks for system administration and monitoring we recommend thatyou create a separate monitor set with the SRMmonitoring area SAP (CEN) EnterpriseBuyerMonitors which includes multiple isolated monitors summarized into one single monitor Thisprovides you with a simple separation between the middleware and SAP SRM Server
Procedure
1 Go to transaction RZ20 and create a newmonitor under the SRMmonitor set created earlier SAP(CEN ) EnterpriseBuyer Monitors
2 On the top level create a virtual node for each of the following areasn Approval
11212008 PUBLIC 2566
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
n Auction
n Bid Invitation
n Component Planningn Confirmation
n Contract Managementn Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cartn User Administration
3 On the second level enter all MTE classes as rule-based monitors for each area as described inthe table below
Node Type Parameter Value
Approval Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Approval
Auction Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_AUC
Bid Invitation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_BID
Component Planning Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
2666 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PM
Confirmation Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Confirmation
Contract Management Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_Contract
Invoice Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_INV
Others Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_OT
Procurement Card Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PC
Purchase Orders Virtual
11212008 PUBLIC 2766
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
Node Type Parameter Value
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_PO
Shopping Cart Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_ShoppingBasket
User Administration Virtual
CCMS_DE-FINE_R3_SYSTEMS
Rule R3System ltSRMSERVER_SYSTEMSgt
R3System ltSRMSERVER_SYSTEMSgt
R3Client ltEBP Clientgt
CCMS_GET_MTE_BY_CLASS_AND_CLIENT
Rule
MTEClass BBP_US
3125 Monitoring SAP SRM-MDM Catalog 30
31251 SAP SRM-MDM Catalog 30
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDMServer SRM Server Transactions are connected to Catalog using Open Catalog Interface
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290
SAP SRM-MDM Catalog 30 uses Data Repository of MDM Core (MDS and MDIS) for processingcombined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3124) for postprocess monitoring takes care of monitoring for SRMMDM CatalogThe following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog
2866 PUBLIC 11212008
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM31 Alert Monitoring with CCMS
31252 GRMG Availability Monitoring for SAP SRM-MDMCatalog 30
The SAP SRM-MDMCatalog runs on the SAP Web Application Server (Java) 701 so the main focus ofmonitoring this component is the monitoring of the SAP J2EE EngineYou can find information about monitoring the Web AS (Java) in the SAP NetWeaver MonitoringSetup Guide (MSG) at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 IncludingEnhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 701Technical Operations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70Including Enhancement Package 1 System Administration Technical Operations Manual
Prerequisites
n Your SRMMDM Catalog is connected to the CENtral monitoring System (CEN) and registeredas a remote system
n The SAPCCMSR agent is registered and running for each SRMMDMCatalog instance
Apart from the SAP J2EE Engine the availability of the SRM MDM Catalog component can bemonitored using the GRMG technology of the CCMS
Procedure
1 Go to transaction RZ20 and create a new monitor SAP SRM-MDM Catalog UI2 On the top level create a virtual node for each of the following areasn J2EE Engine 701 on ltHostnamegtn GRMG Availability Monitor
3 On the second level create rule-based monitors for each area as described in the following table
Node Type Parameter Value
J2EE Engine 700 on ltHostnamegt Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System ltCURRENTgt
Rule R3System ltCURRENTgtCCMS_GET_MTE_BY_CLASS
MTEClass GRMG_ltScenNamegt
11212008 PUBLIC 2966
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
32 Detailed Monitoring and Tools for Problem andPerformance Analysis
321 Component-Specific Analysis Tools
3211 SAP Supplier Relationship Management (SAP SRM) 70
SAP SRM 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solutionSAP SRM 70 application-specific logging information is written into the application log
3212 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
3213 SAP SRM-MDM Catalog 30
SAP SRM-MDM Catalog 30 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual
3066 PUBLIC 11212008
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
httpsaphelpcomnw70 SAP NetWeaver Including Enhancement Package 1 System AdministrationTechnical Operations Manual The SAP SRM Applications Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
322 Scenario Problem Analysis Tools
The following information applies to all SAP SRM 70 business scenarios
3221 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTPFor more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3222 Data Archiving Monitors
For more information see the SAP NetWeaver Monitoring Setup Guide (MSG) athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Operations Monitoring and the SAP NetWeaver 701 Technical Operations Manualat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1System Administration Technical Operations Manual
3223 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define anduse them see the SAP NetWeaver Monitoring Setup Guide (MSG) at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration OperationsMonitoring
11212008 PUBLIC 3166
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
3 Monitoring of SAP SRM32 Detailed Monitoring and Tools for Problem and Performance Analysis
3224 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP EnterprisePortal see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration Technical OperationsManual For information about how to monitor the cache upload of the Business Package for SupplierCollaboration see SAP Note 749231
323 Logs and Trace (Component or Scenario-Specific)
For LACWPS 70 Component specific monitoring
Logging Categories ApplicationsSRMLA
Tracing Locations comsapsrmla
For SRM‒MDM30 Component specific monitoring
Logging Categories ApllicationsMDM
Tracing Locations comsapmdmsrmcat
Logging and tracing for ABAP components is done using transaction SLG1 Each log in the databasealso has the attributes Object and Sub-object These attributes describe the application which wrote thelog and classify this application You can find the object and sub-objects of SAP SRM applicationsin the following list
Software Component Object Sub-object Object text
SAP SRM SERVER SAPSRM All Sub-objects
SAPPSSRM All Sub-objects
BBP Sll Sub-objects
3266 PUBLIC 11212008
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM
4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to middlewaretechnologyYou can find more information about the underlying technology in the Technical Operations Manual athttphelpsapcomnw70 SAP NetWeaver 70 including enhancement package 1 System Administration
Technical Operations Manual
41 Administration Tools of Software Components
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant administration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
42 Software Configuration
All SAP SRM 70 components are technically based on SAP NetWeaver 701 For information onthe relevant configuration tools see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual J2EE based components store their technical configuration parameters in the Configuration Manager(CM) repository For more information see the SAP NetWeaver 701 Technical Operations Manual atat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (ApplicationServer for Java) Management Tools Config Tool
11212008 PUBLIC 3366
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM43 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description
SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP toolfor ABAP-based system used forComponent CustomizingUse transaction SPRO to access theIMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process- andscenario-based configurationSee SAP Note 1230438
43 Starting and Stopping
The following information is scenario-independentStart and Stop Sequence and Tools
Start and Stop Sequence and ToolsSoftware Component
Sequence Tool Documentation
SAP Process IntegrationServer PI (also knownas SAP ExchangeInfrastructure XI)
1 n STARTSAP (UNIX)n SAP Management
Console (Windows)
Enterprise Buyerback-end (OLTP)
2 n STARTSAP (UNIX)n SAP Management
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)n SAP Management
Console (Windows)
TRex 5 n Start Services(Windows)
n Start Daemons (UNIX)
SAP LACWPS 70Only if SAP WebApplication Server701 (Java) is installedstandalone ‒ in case ofAdd-In installation it isstarted together with theSRM Server
6
SAP NetWeaver 701 TechnicalOperations Manual at
httphelpsapcom
SAP NetWeaver SAP NetWeaver70 Including Enhancement Package 1System Administration TechnicalOperations Manual
3466 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM44 Backup and Restore
44 Backup and Restore
To ensure that you can restore and recover your system in case of failure you should back up yoursystem landscape regularlyThe backup and restore procedure for SAP SRM consists of two parts
n Backup and restore for each componentn Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systemsIt should be embedded in your overall business requirements and take into account the overallprocess flow of your companyIn addition the backup concept must cover disaster recovery processes for example loss of yourdata center due to fire Most important in this context is to ensure that backup devices are not lostalong with normal data storage For more information see section 81 Categories of System Components forBackup and Restore [page 55])Based on the type of application data a component holds we have used a categorization scheme thatcan be used to analyze the backup requirements of any system component and to easily determine anappropriate backup method for this component The following table contains the component listof the solution and the appropriate categories
Component Category ApplicationData Type Backup Method forApplication Data
SAP SRM Server XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP LACWPS (Add-InInstallation SRM Server)
XI Original and Replicated n Included in SRMServer
SAP LACWPS (usingstandalone SAP WAS Java)
VIII Original n Data is stored on SRMServer
n Database and logbackup
n File system backup(full andorincremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and logbackup
n File system backup(full andorincremental)
SAP NetWeaver TREX III IV n File system backup
11212008 PUBLIC 3566
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM44 Backup and Restore
441 General Remarks
Caution
This information assumes that readers are familiar with database and server administration andtherefore does not explain how to back up a relational database management system (RDBMS) or afile system If you have questions contact your IT staff and refer to the operations manuals providedby your database and operating system suppliers
SAP solutions use several SAP component systems to implement cross-system processes Data is nolonger held centrally in a single system instead it is distributed between several SAP componentsDue to the non-transactional character of the document workflow between the different landscapecomponents involved within one SAP SRM business scenario it is impossible to find a common pointof consistency across the whole SAP SRM landscapeThe only backup type that can guarantee full physical and logical consistency (these terms areexplained below) of an SAP SRM landscape is an offline backup of the whole landscape conductedafter all business users have logged off and the complete business workflow has ended Tools offeringmanageability and monitoring of these tasks do not yet exist
n Logical ConsistencyRestores the SAPSRM system landscape (cross-system data consistency) to a consistent state Therestoration applies at document level at the time of the backup This includes the successfulroll-back of all open business transactions with respect to the exchange of documents (if a purchaseorder is sent but a purchase order response has not yet been received for example)
n Physical ConsistencyRestores individual SAP SRM components to a consistent state followed by a successful startupof the restored components and a successful reconnection to other components Physicalconsistency provides a working SAP SRM runtime in which newly created business documents canbe exchanged It is required to develop a transactional conduct on user level to react to brokenworkflows and outdated documents appearing after the restoration
A distributed business system landscape requires a detailed B amp R concept This concept mustaccount for both the business data (which is contained in databases) and the runtime infrastructureRegular backups keep the downtime of the system landscape to a minimum during restoration ofthe infrastructure and business data We recommend a backup after the initial installation andconfiguration of the system landscape We also recommend a backup after changes (this meanschanges to the configuration software upgrade of individual components or replacement ofcomponents) are made to the system landscape depending on the frequency of such changesWhen you decide which infrastructure components to back up consider the following factors
n Time required for a complete reinstallationn Time required for additional configuration
3666 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM44 Backup and Restore
n Effects of the expected downtime of one or more infrastructure components with regard to theoverall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRMlandscapeYou must test your BampR concept regularly A single BampR test is insufficient since the SAP SRMlandscape is likely to change and render a given concept redundant System administrators need anup-to-date BampR concept to be able to quickly restore failed systemsFor more Information For more information see the SAP NetWeaver 701 Technical OperationsManual at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package1 System Administration Technical Operations Manual
442 Backup of Individual Components in an SAP SRMLandscape
When you plan a BampR strategy for application software and configuration files you must considerthe following elements
n Operating systemn RDBMS data files
n RDBMS software
n SAP software and file systemsn Log files (SAP and other)n Software of other system components (file systems and configuration files)
Note
A component that has application data (database for example) is usually also comprised ofapplication software and configuration files (runtime infrastructure) that need to be backed upA component that contains no application data may still be comprised of configuration files andsoftware that do require a backup
4421 BampR for Operating System Software andConfiguration Data
Apart from business-critical application data (generally held in databases) it may also be worthwhileto back up the system and application software (including configuration files) If you do this you donot have to reinstall the system and application software if the software becomes damaged
11212008 PUBLIC 3766
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM44 Backup and Restore
While it is always possible to reinstall the operating system software and configuration datareinstallation and configuration take a long time Therefore if a backup of the software andconfiguration is available you can reduce the time needed to restore your system after a system failureWhile data that is contained in the RDBMS can be backed up online it is not possible to do thesame for the runtime infrastructure If you perform a backup while the server is running openfiles 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 thesame for the runtime infrastructureAn online backup refers to the system landscape and not the databases that contain thebusiness-critical application or the infrastructure components
Note
If you perform a backup while the server is running open files may not be backed up
File System Backup Versus Full System Backup
A file system backup only applies to specific files or file systems whereas a full system backup appliesto all files and file systems the operating system
Recommendation
We recommend that you perform a full system backup after installation that you back up the filesystems of both the installed software and the operating system on a regular basisFor more information on possible backup scenarios see SAP Service Marketplace athttpservicesapcomatg Advanced Technology Group Backup amp Restore
4422 Database BampR
Note
We recommend that you run the database in archive mode This means all actions on the databasethat 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 oftransaction logs since the last backup it is possible to restore a crashed database to any point in timebefore the database crashed
Note
We recommend that you back up your database every day with several backups of the log filesduring the day as the log files fill up
3866 PUBLIC 11212008
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM44 Backup and Restore
4423 B amp R for SAP Web Application Server (WebAS) 701
Back up the file system in which the application software is installed
Note
We recommend regular file system backups (at least after software changes and upgrades forexample kernel upgrades and service packs) Perform a full system backup after installation andupgrades of the operating system and the SAP software
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
443 BampR for Individual System Components
4431 SAP Live Auction Cockpit Web Presentation Server(LACWPS) 70
SAP LACWPS 70 is technically based on SAP NetWeaver 701For information about technical problem analysis (for example for database operating systemworkload analysis and so forth) see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual The SAP SRM Application Operations Guide covers only differences and additional informationspecific to the SAP SRM solution
Note
LACWPS uses the SRM Server as its persistence layer therefore detailed problem and performanceanalysis must be done in both the LACWPS and in the SRM Server
4432 SAP SRM-MDM Catalog 30
For more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual
11212008 PUBLIC 3966
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM44 Backup and Restore
444 BampR for a Complete SAP SRM Landscape
4441 Landscape Shutdown
You have to shut down the individual components in the following sequenceSAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed andshut down the underlying RDBMS
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have beenprocessed Shut down the ABAP-based part of SAP SUS and the underlying RDBMS
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS (The J2EE Engine shuts down automaticallywhen back-end is stopped)
4442 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape proceed as described in section in section442 Backup of Individual Components in an SAP SRM Landscape [external document]
Note
When you back up the SAP NetWeaver PI server make sure that you also back up the filesystem This is required because the file system contains the SAP J2EE Engine together with thenecessary configuration files for the system landscape directory and the document transformation(usrsapltSIDgtSYSglobalxi)
4066 PUBLIC 11212008
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM45 System Copy
4443 Landscape Startup
For the startup sequence of the individual components see section 43Starting and Stopping [page 34]
445 BampR for an SAP SRM Business Scenario
To back up an SAP SRM business scenario you have to apply the BampR steps of the components thatcomprise a business scenario For these steps see
n section 442Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 443BampR for Individual System Components [page 39]
To see which components are required for a specific business scenario see section 22Software ComponentMatrix [external document]
45 System Copy
For more information on prerequisites procedures and limitations for copying components of SAPSRM see the SAP NetWeaver 701 system copy guides at httphelpsapcom SAP NetWeaverSAP NetWeaver 70 Including Enhancement Package 1 Installation Configuration Upgrade Installation ampImplementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems
46 Scheduled and Manual Periodical Tasks
461 Periodical Tasks for SAP NetWeaver 701
For more information on standard background jobs and periodical tasks for SAP NetWeavercomponents see the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom
SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
11212008 PUBLIC 4166
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM46 Scheduled and Manual Periodical Tasks
462 Periodical Tasks for SAP SRM 70
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
CLEAN_REQREQ_UP(and START_CLEANER)
Required
BBP_GET_STATUS_2 Required
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO-CAL_ACCOUNT
Optional
BBP_SC_TRANS-FER_GROUPED
Optional
SRM_CALL_HAN-DLER_REPORT
Required
5 to 10 minutes For more information see the SolutionManager content on each SAP SRMscenario you have implemented
The configuration of this job depends on the number of shopping cart items created per week (it isrecommended to run the job twice a day to collect shopping cart items created during the past sevendays and to run it in its entirety during the weekend) The job should be monitored regularly toavoid system resources being utilized completely Only if Records Management is used
463 Periodical Tasks for SAP SRM-MDM Catalog 30
Standard Background Jobs
Program Name Task Required orOptional
RecommendedFrequency
Detailed Description
SRM-MDM_CTR_TRANSFER
Optional Daily This report is only required if contracts arenot distributed automatically It initiatesthe transfer of all contracts that are flaggedfor distribution
For more information see the MDM 55 Solution Operation Guide on SAP Service Marketplaceat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1Installation Configuration Upgrade Installation amp Implementation Documentation Center Operations SAPNetWeaver MDM SAP NetWeaver MDM Documentation
4266 PUBLIC 11212008
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM47 Log on and Load Balancing
464 Manual Periodical Tasks for SAP SRM 70
For more information on the required manual periodical tasks for the SRM Server see the sectionReports on httphelpsapcom SAP Business Suite SAP Supplier Relationship Mgmt SAP SRM70 (under Overview)
Note
There are no periodical tasks for the Live Auction Cockpit
47 Log on and Load Balancing
As a web-based application the basis for logon and load balancing in SAP SRM is a high availabilitylandscape setup together with a load balanced network setup
n For more information on network load balancing see the Technical Infrastructure Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1
Installation Configuration Upgrade Installation amp Implementation Documentation Center Installation
n For information on load balancing between many Java instances and on the SAP Web Dispatchersee the SAP NetWeaver 701 Technical Operations Manual at httphelpsapcom SAPNetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System Administration TechnicalOperations Manual
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRMServer can be used to redirect certain users to specific application servers
48 User Management
All scenarios and components in SAP SRM use the user management functions provided by SAPNetWeaver 701For more information about user administration and authentication see the SAP SRM SecurityGuide at httpservicesapcominstguides Installation amp Upgrade Guides SAP Business SuiteApplications SAP SRM SAP SRM Server 70 Because of special requirements of the SAP SRM Server the following SAP SRM-specific usermanagement tools are also availableUser Management Tools (SAP SRM Server)
11212008 PUBLIC 4366
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM48 User Management
Tool Detailed Description Comments
Self Registration ‒ SRM Server httphelpsapcom SAPBusiness Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on UserSelf-Registration (underOverview Getting Started )
Manage User Data(BBPUSERMAINT) ‒ SRMServer
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on User andEmployee Date (underMaster Data)
User management for supplierself-services - SRM Server (SUS)
httphelpsapcom
SAP Business Suite SAP SupplierRelationship Management SAP SRM70
See the section in thedocumentation on ExternalBusiness Partners (under FunctionsGlobal Functions )
External suppliers can also act as bidders in SAP SRM Server SUS scenarios The users of thesesuppliers need to be created in SAP SRM Server with the same user ID (this can be done via replicationfrom SUS)For more information see the SAP SRM 70 Solution Manager Content under SAP Solution Managerunder ltproject namegt Configuration SAP SRMltreleasegt Basic Settings for Service Procurement Classic
481 Portal User Management
For user management of SAP Enterprise Portal see the Portal Security Guide athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4811 Activating the TPD for User Integration Between SAPSRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory(TPD) of the SAP Enterprise Portal (EP)
PrerequisitesYou are logged on to theAdministrator of the J2EE Engine in the Visual Administrator console of SAP J2EE EngineYou have deployed the TPD Software Deployment Archive (SDA) and the Business Package forSupplier Collaboration 40 using the Software Deployment Manager (SDM) at the same time
4466 PUBLIC 11212008
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM48 User Management
Procedure
1 Check that TPD SDA has been deployed by performing the following stepsa) Start SDM by running ltportal installation directorygtusrsapltdb
instancegtJC00SDMprogramRemoteguibat
b) Log on by choosing the icon with the quick info text Connectc) Choose SAPJ2EEEngine SUP-PORTAL d) Check that the list includes the srmsuptpdimpl SDAe) If you cannot find TPD SDA you must deploy it manually
2 On the Visual Administrator screen in the left screen area choose Server 0 xxxxx ServicesConfiguration Adapter
3 In the right screen area choose cluster_data server cfg services 4 Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode5 Open Propertysheetcomsapsecuritycoreumeservice6 Select the properties shown in the following table and enter the corresponding values in the
Custom field
Property Value
umetpdclassloader librarysrm~suptpdimpl
umetpdimpclass comsapccsupcommontpdSPPartnerDirectoryImpl
7 Each time you add a value choose Apply Custom8 Restart SAP J2EE Engine to activate the TPD
If SAP J2EE Engine does not restart there may be a typing error in one of the properties you editedCheck the properties and make any necessary corrections then restart SAP J2EE Engine againFor more information about the SAP User Management Engine see the Portal Security Guideat httphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 SystemAdministration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guidesfor Usage Types EPC and EP
4812 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence storeand they have not been created in SAP Enterprise Portal you must assign business partners to theusers Users must have a business partner relationship that is reflected in SAP Enterprise Portal
11212008 PUBLIC 4566
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
4 Management of SAP SRM48 User Management
PrerequisitesYou are logged on to SAP Enterprise Portal as a portal administrator and you have activated theTrading Partner Directory (TPD) for SAP Enterprise Portal see section 4811Activating the TPD for UserIntegration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44]
Procedure
1 In the User Administration workset choose User Administration Users Search 2 In the Search field enter the name of a user or enter to search for all users and then choose Enter3 ChooseModify next to the user that you want to modify4 Select a company for the user5 Save your changes
Note
We recommend that you assign a business partner to a user immediately after you create the user
4666 PUBLIC 11212008
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM if that componentshould become unavailable
Component Business Impact if Unavailable
SAP SRM 70 Business critical single point of failure for allscenarios
SAP LACWPS 70 Live auctions will not be available in the StrategicSourcing scenarioBusiness critical impact if the component becomesunavailable while one or more live auctions are activeThe auction outcome may differ significantly fromwhat it would have been if the component had notbecome unavailableLive auctions do not need to be available 24 x 7
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only haveasynchronous messaging availableDocument delivery is delayed but not cancelled
SAP NetWeaver Enterprise Portal 70 As all scenarios are only available via the Portal afailure would be critical
For more information about high availability and switchover see the SAP NetWeaver 701 TechnicalOperations Manual at httphelpsapcom SAP NetWeaver SAP NetWeaver Including EnhancementPackage 1 System Administration Technical Operations Manual See the section on high availability in theManual under General Administration Tasks
11212008 PUBLIC 4766
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
This page is left blank for documentsthat are printed on both sides
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
6 Software Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution maintenance andtesting procedures for complex software landscapes and multiple software development platformsThe goal of Software Change Management is to establish consistent solution-wide changemanagement that allows for specific maintenance procedures global rollouts including localizationsand open integration with third-party productsThis section provides additional information about the most important software componentsThe following topics are covered
n Transport and Change ManagementEnables and secures the distribution of software changes from the development environment tothe quality assurance and productive environment
n Development Request and Development Release Managementn Template Management
Enables and secures the rollout of global templates including localizationsn Quality and Test Management
Reduces the time costs and risks associated with software changesn Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance proceduresn Release and Upgrade Management
Reduces the time costs and risks associated with upgrades
61 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing and then transport thechanges between the SAP Systems in your system landscapeFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver 70 Including Enhancement Package 1 System
Administration Technical Operations Manual SAP SRM 70 can be used with more than one portal tenant and in several different ways
n One option is for one portal tenant to be used for SAP SRM Server another one for SAP SRMServer (SUS) and a third one for SAP NetWeaver BI
11212008 PUBLIC 4966
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
6 Software Change Management62 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assigndifferent purchasing organizations to different portal tenants ‒ each purchasing organization hasa separate portal tenant This is useful for example if the SRM Server is provided to differentcompanies by an application service provider
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAPNetWeaver Process Integration and SAP NetWeaver Enterprise Portal
62 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscapeIt is an efficient method of transporting a selected number of requests into a group of transporttargets and uses clearly defined approval steps to ensure the quality of your target systemsFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual
63 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 70 can be found in the ReleaseInformation Notes (RIN) for each SPSupport packages for components based on the SAP NetWeaver Application Server (ABAP) (such asSAP SRM Server) are applied using the Support Package ManagerSupport packages and patches for components based on the SAP NetWeaver Application Server (Java)for example SAP LACWPS are deployed using the Software Deployment ManagerFor more information see the SAP NetWeaver 701 Technical Operations Manual athttphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
Administration Technical Operations Manual Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAPNetWeaver Support Package Stack guides at httphelpsapcom SAP NetWeaver SAPNetWeaver Including Enhancement Package 1 Installation Configuration Upgrade Installation amp ImplementationDocumentation Center Maintenance SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant For more information seehttpservicesapcomnote-assistant
5066 PUBLIC 11212008
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
6 Software Change Management64 Release and Upgrade Management
64 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 70 System Status
LAC WPS 70 System InfohttpltservergtltportgtsapmonitoringComponentInfo
n The versions of all components can be displayed centrally in the Solution ManagerFor more information see the information available on SAP Service Marketplace athttpservicesapcomsolutionmanager
n For SAP SRM release and upgrade plans see the information available on SAP Service Marketplaceat httpservicesapcomsrm
65 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing BusinessConfiguration Sets
66 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP)For more information see httphelpsapcom SAP NetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability Testing For more information on testing software changes based on SAP NetWeaver Appication Server (Java)see httphelpsapcom SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology JavaDevelopment Manual
11212008 PUBLIC 5166
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
This page is left blank for documentsthat are printed on both sides
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 70For more information about these services see SAP Safeguarding on SAP Service Marketplace athttpservicesapcomsafeguarding
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types isavailable in the SAP NetWeaver Problem Analysis Guide (PAG) at httphelpsapcom SAPNetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability
Possible problem situations using SAP SRM 70
Problem Application components Information
No monitoring information isdisplayed in the CCMS AlertMonitor (transaction RZ20) ofthe central monitoring SAP WebAS ABAP system Howevermonitoring information is availablein the Visual Administrator of theJ2EE server for example statusinformation in the J2EE statusmonitors
All SAP SRM applicationcomponents
See the CCMS MonitoringInfrastructure ProblemAnalysis Guide in the PAG at
httphelpsapcom SAPNetWeaver SAP NetWeaver IncludingEnhancement Package 1 Functional ViewSAP NetWeaver by Key Capability
Solution Life Cycle Management by KeyCapability SAP NetWeaver PAGUsage Type Application Server ABAP
Portal restriction for SAPSRM-MDM Catalog
SAP SRM-MDM Catalog 20 Refer SAP Note 1147103
Error ldquoPage not found or notavailablerdquo while accessing a catalogconfigured in the SRM Server
Business Packages for SAP SRM Refer SAP Note 1260119
For troubleshooting SAP NetWeaver MDM see httpservicesapcominstallMDM
Operations MDM 55 SP06 - Solution Operation Guide
11212008 PUBLIC 5366
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
This page is left blank for documentsthat are printed on both sides
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
8 Appendix
8 Appendix
81 Categories of System Components for Backup andRestore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
I Only software noconfiguration orapplication data
n No backup newinstallation in caseof a restore or
n Initial software backupafter installation andupgrade
n Backup of log files
BDOC-modeler
II Only softwareand configurationinformation noapplication data
n Backup after changeshave been applied or
n No backup newinstallation andconfiguration in caseof a restore
n Backup of log files
SAP Gateway CommStationSAP Business Connector
III Only replicatedapplication datareplication time issufficiently small for arestore
Datan No data backup
neededBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
IV Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Application-specific
file system backup orn Multiple instancesBackup of softwareconfiguration log files
SAP IMS Search engineWebserver
V Only replicatedapplication data backuprecommended becausereplication time is toolong data managed by aDBMS
Datan Database and log
backup orn Multiple instancesBackup of softwareconfiguration log files
Catalog Server
11212008 PUBLIC 5566
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
8 Appendix81 Categories of System Components for Backup and Restore
Categories of SystemComponents Category Properties
Suggested Backup andRecovery Methods Example
VI Original application datastandalone system datanot managed by a DBMS
Datan Application-specific
file system backupBackup of softwareconfiguration log files
Webserver
VII Original application datastandalone system datamanaged by a DBMS notbased on SAP NW AS
Datan Database and log
backupBackup of softwareconfiguration log files
VIII Original application datastandalone system basedon SAP NW AS
Datan Database and log
backup applicationlog backup
Backup of softwareconfiguration log files
Standalone SAP system
IX Original applicationdata data exchange withother systems data notmanaged by a DBMS
Datan Application-specific
file system backupdata consistency withother systems must beregarded
Backup of softwareconfiguration log files
X Original application datadata exchange with othersystems data managedby a DBMS not based onSAP NW AS
Datan Database and
log backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP liveCacheSAP MobileWorkbench
XI Original application datadata exchange with othersystems based on SAPNW AS
Datan Database and log
backup applicationlog backup dataconsistency withother systems must beregarded
Backup of softwareconfiguration log files
SAP systemSAP CRMSAP NW BI
5666 PUBLIC 11212008
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
8 Appendix82 Related Information
82 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 UpgradeGuides
httpservicesapcominstguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM Server 70
SAP Notes httpservicesapcomnotes
Released Platforms httpservicesapcomplatforms
Network Security httpservicesapcomsecurityguide
SAP NetWeaver Technical Operations Manual httphelpsapcom SAP NetWeaver SAPNetWeaver 70 Including Enhancement Package 1 SystemAdministration Technical Operations Manual
SAP Solution Manager httpservicesapcomsolutionmanager
11212008 PUBLIC 5766
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
This page is left blank for documentsthat are printed on both sides
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
A Reference
A Reference
A1 The Main SAP Documentation Types
The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software
Figure 6 Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages aswell as many glossary entries in English and German
n Target groupl Relevant for all target groups
n Current versionl On SAP Help Portal at httphelpsapcom Additional Information Glossary (direct
access) or Terminology (as terminology CD)l In the SAP system in transaction STERM
11212008 PUBLIC 5966
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
A ReferenceA1 The Main SAP Documentation Types
SAP Library is a collection of documentation for SAP software covering functions and processes
n Target groupl Consultants
l System administratorsl Project teams for implementations or upgrades
n Current versionl On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions forraising security levels A collective security guide is available for SAP NetWeaver This documentcontains general guidelines and suggestions SAP applications have a security guide of their own
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
Themaster guide is the starting point for implementing an SAP solution It lists the requiredinstallable units for each business or IT scenario It provides scenario-specific descriptions ofpreparation execution and follow-up of an implementation It also provides references to otherdocuments such as installation guides the technical infrastructure guide and SAP Notes
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit takinginto account the combinations of operating systems and databases It does not describe anybusiness-related configuration
n Target groupl Technology consultantsl Project teams for implementations
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform One of its main functions is the configuration of business and IT scenarios It containsCustomizing activities transactions and so on as well as documentation
6066 PUBLIC 11212008
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Solution consultants
l Project teams for implementationsn Current versionl In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP systemThe Customizing activities and their documentation are structured from a functional perspective(In order to configure a whole system landscape from a process-oriented perspective SAP SolutionManager which refers to the relevant Customizing activities in the individual SAP systems is used)
n Target groupl Solution consultants
l Project teams for implementations or upgradesn Current versionl In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver and precedes the solution operations guide The manual refers users to the tools anddocumentation that are needed to carry out various tasks such as monitoring backuprestoremaster data maintenance transports and tests
n Target groupl System administrators
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks
n Target groupl System administratorsl Technology consultantsl Solution consultants
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution It provides scenario-specific descriptions of preparation execution and follow-up of anupgrade It also refers to other documents such as the upgrade guides and SAP Notes
11212008 PUBLIC 6166
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
A ReferenceA1 The Main SAP Documentation Types
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into accountthe combinations of operating systems and databases It does not describe any business-relatedconfiguration
n Target groupl Technology consultantsl Project teams for upgrades
n Current versionl On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG)
n Target groupl Consultants
l Project teams for upgradesn Current versionl On SAP Service Marketplace at httpservicesapcomreleasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
6266 PUBLIC 11212008
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in thedocumentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options
n Cross-references to other documentation or published works
Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11212008 PUBLIC 6366
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2009 SAP AG All rights reserved
Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty
This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1
6466 PUBLIC 11212008
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides
11212008 PUBLIC 6566
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice