operations guide for sap risk management 12.0 sp11

Operations Guide | PUBLIC2021-03-18

Operations Guide for SAP Risk Management 12.0 SP11

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 Global Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Technical System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1 Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Monitoring of the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.1 CCMS Monitor Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.2 Alert Monitoring with CCMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Component-Specific Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.3 Detailed Monitoring and Tools for Problem and Performance Analysis. . . . . . . . . . . . . . . . . . . . . . . 17

Trace and Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Operating System Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Workload Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Other Important Problem Analysis and Monitoring Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Interface Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.4 Important Application Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4 Managing the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244.1 Starting and Stopping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.2 Backup and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.3 System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.4 Periodic Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Scheduled Periodic Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.5 Load Balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264.6 User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.7 Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5 High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

6 Software Change Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296.1 Transport and Change Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296.2 Development Requests and Development Release Management. . . . . . . . . . . . . . . . . . . . . . . . . . . 296.3 Quality Management and Test Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.4 Support Packages and Patch Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

7 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

8 Configuring Remote Connection to SAP Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2 PUBLICOperations Guide for SAP Risk Management 12.0 SP11

Content

8.1 Read Only Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

9 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339.1 Categories of System Components for Backup and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339.2 Related Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Operations Guide for SAP Risk Management 12.0 SP11Content PUBLIC 3

1 Getting Started

The Operations Guide provides administration information for SAP Risk Management.

SAP Risk Management enables organizations to balance business opportunities with financial, legal, and operational risks to minimize the market penalties from high-impact events. The application allows customers to identify these risks and monitor them on a continuous basis. Stakeholders and owners are provided with such tools as analytic dashboards for visibility in mitigating risks in their areas of responsibility.

About this Guide

This guide provides a starting point for managing your SAP application and maintaining and running it. It contains information for tasks and lists the tools to implement them. This guide also provides references to the documentation required for these tasks.

NoteThe guide refers to the SAP NetWeaver Operations Guide as most production operation tasks are done at the server level. The application tasks are in the Monitoring and Management sections.

NoteOccasional references may be made in this guide to other applications from the SAP governance, risk and compliance solutions (GRC), such as SAP Process Control or SAP Access Control. Note that the use of those other applications requires that you have also implemented them and possess the corresponding license.

CautionThis guide does not replace the daily operations handbook that we recommend customers create for their production operations.

Target Groups

The guide is written for the following audiences:

● Technical Consultants● System Administrators● Solution Consultants● Business Process Owner● Support Specialist


Getting Started

1.1 Global Definitions

SAP Application:

An SAP software solution that serves a specific business area like ERP, CRM, PLM, SRM, SCM.

Business Scenario:

From a microeconomic perspective, a business scenario is a cycle that consists of several different interconnected logical processes in time. A business scenario includes several company departments and business partners. From a technical point of view, a business scenario needs at least one SAP application (SAP ERP, SAP SCM, or others) for each cycle and possibly other third-party systems. A business scenario is a unit that can be implemented separately and reflects the customer’s prospective course of business.

Component:

The smallest individual unit considered within the Solution Development Lifecycle. Components are separately produced, delivered, installed, and maintained.

1.2 Important SAP Notes

For a list of important SAP Notes for SAP Risk Management, see the SAP Risk Management 12.0 Master Guide at http://help.sap.com/rm .

Operations Guide for SAP Risk Management 12.0 SP11Getting Started PUBLIC 5

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Frm

2 Technical System Landscape

For information about the technical system landscape and the software component matrix, see the SAP Risk Management 12.0 Master Guide at http://help.sap.com/rm .

2.1 Related Documentation

For more information about the technical system landscape, see the guides in the following table.

Topic Guide/Tool Link on SAP Help Portal

Application and industry specific components such as SAP Financials and SAP Retail

Master Guide https://help.sap.com/

Technology Components such as SAP NetWeaver Application Server

Technical Configuration

Sizing Quick Sizer Tool https://www.sap.com/about/benchmark/sizing.html

Installation Installation Guide https://help.sap.com/viewer/p/SAP_RISK_MANAGEMENT

Security Security Guide https://help.sap.com/viewer/p/SAP_RISK_MANAGEMENT


Technical System Landscape

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Frm

http://help.sap.com/disclaimer?site=https%3A%2F%2Fhelp.sap.com%2F

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwww.sap.com%2Fabout%2Fbenchmark%2Fsizing.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwww.sap.com%2Fabout%2Fbenchmark%2Fsizing.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fhelp.sap.com%2Fviewer%2Fp%2FSAP_RISK_MANAGEMENT




3 Monitoring of the Application

The information in this section applies to SAP Risk Management. Within the management of SAP Technology, monitoring is an essential task. The Computing Center Management System (CCMS) is a set of integrated tools for monitoring and administration of SAP system landscapes. The transaction code is RZ20.

RecommendationFor more information about the underlying technology, see the Technical Operations for SAP NetWeaver at http://help.sap.com/netweaver under SAP NetWeaver Platform System Administration and Maintenance Information .

3.1 CCMS Monitor Templates

This section lists the CCMS monitor sets you can use to monitor the application components. The CCMS Monitor Templates include the following:

● Background processing● Performance overview● Syslog

The SAP Web Service Monitor Template is Web Service Monitor.

Operations Guide for SAP Risk Management 12.0 SP11Monitoring of the Application PUBLIC 7

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnetweaver

CCMS Monitor Template and Web Service Monitor

3.2 Alert Monitoring with CCMS

Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system environment. SAP provides you with the infrastructure needed to set up your alert monitoring to recognize situations for SAP Risk Management as quickly as possible.

Recommendation

To enable the auto-alert mechanism of CCMS, see SAP Note 617547 .

3.2.1 Component-Specific Monitoring

NoteThe following includes information relating to SAP Process Control and SAP Access Control. References to those applications are only relevant if you have implemented and licensed them in addition to SAP Risk Management.


Monitoring of the Application

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/617547

You monitor the following data in the SAP Standard CCMS tool for SAP Risk Management:

● Background job● Performance Overview● DB access time● System log● System errors● Web Services Call

Background Jobs

You monitor the background job status for jobs that are aborted, canceled, or have been running for a long time.

ExampleThis is an example of background jobs with the status of Long Running Jobs and Aborted Jobs:

Background Jobs with status of Long Running Jobs and Aborted Jobs


ExampleThe following graphic illustrates that BFC_001 through BFC_005 jobs have the status of Canceled:

Job Overview

You can check the details of canceled jobs by selecting a job and clicking Step. The following graphic is an example of the details for a selected job.

NoteThe Program name/command for the applications start with GRAC, GRPC, or GRFN. They should be alerted.



Details of a Job

Performance Overview

In the Performance Overview CCMS Monitor Templates, look for processes with a high Response Time.

Note● SAP Access Control processes begin with GRAC.● SAP Process Control processes begin with GRPC.● SAP Risk Management processes begin with GRFN.

ExampleThe following figure illustrates that the GR4 system has a response time of 1448 milliseconds.


System Response Time



ExampleThe following graphic illustrates an example of an SAP Process Control process (GRPCRTA_PC):

Workload in System

System Logs

Monitor system logs for any errors.

ExampleThe following graphic illustrates that the R3Syslog displays a runtime error.


Runtime error

You can review the System Log (Syslog): Local Analysis for errors.

Note● SAP Access Control transaction codes start with GRAC.● SAP Process Control transaction codes start with GRPC.● SAP Risk Management transaction codes start with GRFN.



ExampleThe following graphic illustrates local analysis of SAP Process Control transaction codes:

Local Analysis

System Errors

You review the CCMS Monitor Templates (System Errors) for error messages.


ExampleThe following graphic illustrates system errors such as Aborted Batch Jobs and Update Errors:

System Errors

Web Services

You monitor the SAP Web Service Monitor Templates for errors.

ExampleThe following graphic illustrates the following monitors:

● Task Watcher● Supervisor Destination● Web Services Reliable Messaging (WSRM) Event Handler● Web Services (WS) Namespace for Inbound Destinations● WS Service Destinations



Monitors

3.3 Detailed Monitoring and Tools for Problem and Performance Analysis

SAP Risk Management is based on SAP NetWeaver AS for ABAP 7.52.

RecommendationFor information about technical problem analysis (such as database, operating system, or workload analysis) see the Technical Operations Manual for SAP NetWeaver at http://help.sap.com/netweaver

SAP NetWeaver AS for ABAP 7.52 SAP NetWeaver Platform Technical Operations for SAP NetWeaver .



3.3.1 Trace and Log Files

NoteReferences to other applications of the SAP governance, risk and compliance solutions (GRC), such as SAP Access Control and SAP Process Control, are only relevant if you have also implemented and licensed those applications.

Trace files and log files are essential for analyzing problems. You can use SAP NetWeaver transactions, such as ST22 and SM2, to monitor trace and log files.

RecommendationFor more information, see the Technical Operations Manual for SAP NetWeaver at http://help.sap.com/netweaver SAP NetWeaver AS for ABAP 7.52 SAP NetWeaver Platform Technical Operations for SAP NetWeaver .

Additionally, the GRC applications use the SAP NetWeaver application log to store application error warning and success messages issued in critical processes. For example, the delivery interface between ERP and Process Control, or in UI transactions, stores the messages in the SAP NetWeaver application log. For UI transactions, the application log must be explicitly saved by the user.

Recommendation

For more information about application logs, see http://help.sap.com/netweaver SAP NetWeaver AS for ABAP 7.52 Application Help SAP NetWeaver Library: Function-oriented View Solution Life Cycle Management Application Log (BC-SRV-BAL) .

Application Logs – The application logs can be monitored with transaction SLG1.

● The SAP Risk Management log object is GRRM.● The shared components log object is GRFN.

The following tables list the log subobjects:

SAP Risk Management Log Subobjects

Log Object Log Subobjects Description

GRRM AGGR_RUN Aggregation Run

GRRM ANLS_AUTOMATION Analysis Automation

GRRM CLEANUP Cleanup report to delete transaction data

GRRM CONTEXT Context Values

GRRM KRI KRI runtime

GRRM MIGRATION Migration







GRRM RESPONSE_NOTIF Response Due Date Notification

GRRM RESP_AUTOMATION Response Automation

GRRM SURVEY Survey

GRC Foundation (shared) Log Subobjects


GRFN AC_PROV Access Control Provisioning Engine

GRFN AC_REP Access Control Repository

GRFN API GRC API logging

GRFN ASYNC_UPDATE Asynchronous Update Infrastructure

GRFN AUTH GRC authorization

GRFN CASE_INT Continuous monitoring case integration

GRFN FDS Continuous monitoring flexible data store

GRFN HRMAINT Access to HR ORG maintenance

GRFN IO_EXPORT IO Export

GRFN IO_IMPORT IO Import

GRFN IO_META IO Metadata

GRFN JOB AMF Job Step Execution

GRFN JOB_DESIGN AMF Job Step Design Time

GRFN MDCHECK Master Data Consistency Check

GRFN MIGRATION GRC migration

GRFN MSMP_WF_CN Multi-Stage Multi-Path (MSMP) Workflow – Configuration

GRFN MSMP_WF_NT Multi-Stage Multi-Path (MSMP) Workflow – Notification

GRFN MSMP_WF_RT Multi-Stage Multi-Path (MSMP) Workflow – Runtime



GRFN OWP Offline Workflow Process

GRFN POLICY Policy Management

GRFN REPLACEMENT GRC replacement

GRFN REP_ENGINE Reporting engine

GRFN RISK_AGGR Risk Aggregation

GRFN RM_BANKING Operational Risk Management for Banking Industry

GRFN SURVEY Survey planning

Job Logs – You can view job logs using transaction SM37.

Workflow Item Logs – You can view the workflow item logs using transaction SWI1.

Recommendation

For more information, see the SAP Help Portal at http://help.sap.com and search for SAP Workflow Administration.

For a description of the tasks containing data growth, see the Periodic Tasks [page 25] section in this guide.

3.3.2 Operating System Monitors

SAP Risk Management uses the standard tools for this function available in the SAP NetWeaver AS for ABAP 7.52 and does not require a component-specific tool.

RecommendationFor information, see the Technical Operations Manual for SAP NetWeaver at http://help.sap.com/netweaver


3.3.3 Workload Monitors




http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com





Components to Monitor

Component Monitor Description

Datamart GRFN_DATAMART_UPLOAD_BTC This is the reporting component.

KRI Runtime GRRM_KRI_RUNTIME Periodic runtime of KRIs.

3.3.4 Other Important Problem Analysis and Monitoring Tools




3.3.5 Interface Monitors

Interface monitors analyze problems with interfaces such as RFC, IDoc, and HTTP. SAP Risk Management uses the standard tools for this function available in the SAP NetWeaver AS for ABAP 7.52 and does not require a component-specific tool.










3.4 Important Application Objects

We recommend you monitor the following SAP Process Control, SAP Risk Management and SAP Access Control objects, depending on which of those three GRC applications you have implemented and licensed:

Objects to Monitor

Object Tools Description

Process Overview Transaction SM50 The monitor tracks the amount of time critical processes such as dialog (DIA), update (UPD), or background (BGD) have been running. Processes that have been running too long are shown in red in the runtime column.

Ensure there are enough background work processes on the GRC system. You can use operation mode to switch work processes.

Background Process Transaction SM37 Select the jobs by job name, user name, status, and time period to display a status overview of scheduled jobs. Look for any canceled jobs.

Process Control and Risk Management Application Logs

Transaction GRFN_LOG_ENABLE Enable logging for the following subobjects if you need to track errors in API or authorization check areas:

● API — GRC API Logging

● AUTH — GRC Authorization

For troubleshooting, enable logging for REP_ENGINE — Reporting Engine.

For more information about objects and subobjects, see Trace and Log Files.

Application Logs Transaction SLG1 Enable the GRPC application logs for potential risk areas, such as API access and authorization. Using transaction

SPRO, select Governance, Risk and

Compliance Process Control

Administration Programs

For more information, see Trace and Log Files [page 18].



Object Tools Description

CCMS Transaction RZ20 Monitor the following:

● SAP buffer configuration● Database workload● Operating system workload● System logs for errors● System errors for application

dumps● Workload analysis for any perform

ance issues

For more information, see the Technical Operations Manual for SAP NetWeaver at http://help.sap.com/netweaver

SAP NetWeaver AS for ABAP 7.52

SAP NetWeaver Platform Technical

Operations for SAP NetWeaver .

Shared Objects Memory Transaction SHMM Transaction SHMM provides an overview of the area instances in the shared objects memory of the current application server.

Workflow event queue SWEQADM Use the event queue to delay the starting of receivers reacting to a triggering event. This spreads the system load over a longer time period to combat the threat of system overload. The system administrator sets the event queue.

SICF Transaction SICF Use this transaction to activate Internet services, Web services, and Web Dynpro.

SIGS Transaction SIGS Use this transaction to view the status of IGS services and the required parameters.



4 Managing the Application

SAP provides you with an infrastructure to help your technical support consultants and system administrators manage all SAP components and complete tasks related to administration and operation. The underlying technology of SAP Risk Management is based on SAP NetWeaver.

4.1 Starting and Stopping

SAP Risk Management is provided as an add-on component for SAP NetWeaver. You start and stop it with SAP NetWeaver Web Application Server.

RecommendationFor more information about STARTSAP/STOPSAP and SAPMMC, see the Technical Operations Manual for SAP NetWeaver at http://help.sap.com/netweaver SAP NetWeaver AS for ABAP 7.52 SAP NetWeaver Platform Technical Operations for SAP NetWeaver .

4.2 Backup and Restore

You need to back up your system landscape regularly to ensure that you can restore and recover it in case of failure. All application data for the applications reside in the underlying database. No special backup and recovery methods apply for this component.

The applications rely on the SAP NetWeaver ABAP standard capabilities for the technical operations. The configuration data is stored in the Customizing database tables. These settings are established during the Customizing activities during implementation (transaction SPRO).

NoteIf you use a document management system (DMS) that stores data outside of the underlying database, refer to the backup and restore recommendations for that DMS.

4.3 System Copy

For a system copy of SAP Risk Management, the standard procedures of SAP NetWeaver apply.


Managing the Application


RecommendationHeterogeneous system copies are performed on request and on a project basis.

For more information, see the Technical Operations Manual for SAP NetWeaver at http://help.sap.com/netweaver SAP NetWeaver AS for ABAP 7.52 SAP NetWeaver Platform Technical Operations for SAP NetWeaver .

NoteA client copy from one system into another system with a different operating system or database is not an alternative to a complete heterogeneous migration. For example, client copies do not ensure that all repository changes are taken over into the new system. Therefore, if you want to change your database or application server platform, a heterogeneous system copy is the only procedure that ensures full data replication.

4.4 Periodic Tasks

In addition to the standard jobs mentioned in the Technical Operations Manual for SAP NetWeaver, SAP Risk Management-specific jobs must be scheduled in your system. Run all jobs, unless otherwise specified, at times of minimal system activity (so as not to affect performance or otherwise disrupt your daily operations). All jobs can be restarted. There are no dependencies between the jobs.

4.4.1 Scheduled Periodic Tasks

This information applies to SAP Access Control, SAP Process Control and SAP Risk Management, depending on which of those applications you have implemented and licensed. This information describes the tasks required to keep the application running smoothly. You can configure the tasks to automatically run. It is important that you monitor the execution of these tasks on a regular basis. The tasks are scheduled using transaction SM36, except for the Background Job for Missed Deadlines, which uses transaction SWU3.

Scheduled Periodic Tasks

Program Name/Task Recommended Frequency Description

Schedule Background Job for Missed Deadlines

Every 3 minutes Specify a time interval at which the background job is called regularly. With each execution, the background job checks whether new deadlines have been missed since the last time it ran.

Operations Guide for SAP Risk Management 12.0 SP11Managing the Application PUBLIC 25



Program Name/Task Recommended Frequency Description

Schedule Job for Sending E-Mail Every 3 minutes This program checks whether there are new work items for Process Control and Risk Management, and determines the e-mail addresses of the work item recipients.

GRFN_AM_JOBSTEP_MONITOR Hourly The monitoring program to update job / job step status.

/GRCPI/GRIA_AM_CHANGELOG (in plug-in system. Process Control only)

Daily This program captures the GRC PC change log.

Transfer Work Items to Replacement Daily The program transfers work items from users that are no longer working in Process Control and Risk Management to the replacement users entered in the system for these users.

Maintain DataMart Daily Schedule the report GRFN_DATAMART_MAINTAIN. This can be used for maintaining and uploading the data to DataMart.

Execute KRI Queries and Evaluate Business Rules

(Risk Management only)

Daily Schedule the report GRRM_KRI_RUNTIME. You schedule this job to query the KRI values from the source systems, such as SAP NetWeaver Business Warehouse or SAP ERP, and the business rules are evaluated to attain risk alerts.

Carryforward after Sign-Off

(Process Control only)

After event Schedule the program close (GRPC_CLOSING_BACKGROUND). Once sign-off has been performed for an organization, the program copies any open cases to the new timeframe, and clears the workflows.

Document Copy after Sign-Off

(Process Control only)

After event Schedule a job so that, after tasks have been carried forward into a new timeframe, the documents for those tasks are also copied into the new timeframe. This applies to documents that were created for issues or remediation plans during assessment and tests.

4.5 Load Balancing

SAP Risk Management uses SAP NetWeaver for load balancing.


Managing the Application


4.6 User Management

SAP Risk Management uses SAP NetWeaver for user management.

RecommendationFor more information, see the documentation on the SAP Help Portal at https://help.sap.com/viewer/p/SAP_NETWEAVER .

For specific user management and authorization functions, see the SAP Risk Management 12.0 Security Guide available at https://help.sap.com/rm.

4.7 Printing

SAP Risk Management uses SAP NetWeaver for printing.


Operations Guide for SAP Risk Management 12.0 SP11Managing the Application PUBLIC 27



http://help.sap.com/disclaimer?site=https%3A%2F%2Fhelp.sap.com%2Fviewer%2Fp%2FSAP_NETWEAVER

http://help.sap.com/disclaimer?site=https%3A%2F%2Fhelp.sap.com%2Fviewer%2Fp%2FSAP_NETWEAVER

https://help.sap.com/rm



5 High Availability

Use

SAP Risk Management uses SAP NetWeaver for high availability.

The application follows the general high availability concept for all SAP NetWeaver based systems. You can find more information under SAP NetWeaver AS ABAP: High Availability on the SAP Help Portal at http://help.sap.com, or on the SAP Community Network at https://www.sap.com/community.html

Integration

Recommendation

For more information, see the documentation at http://www.sdn.sap.com/irj/sdn/ha .


High Availability

https://help.sap.com/saphelp_nw70/helpdata/en/3a/9659c492818e468ddf0cc0391c03b1/frameset.htm

http://help.sap.com

http://help.sap.com

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwww.sap.com%2Fcommunity.html

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sdn.sap.com%2Firj%2Fsdn%2Fha

6 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, and testing procedures for software landscapes and multiple software development platforms. These functions support your project teams, development teams, and application support teams.

Software Change Management establishes solution-wide change management that allows for specific maintenance procedures, global rollouts (including localizations), and open integration with third-party products.

This section provides additional information about the most important software components.

The following topics are covered:

● Transport and Change Management:Enables and secures the distribution of software changes from the development environment to the quality assurance and production environment.

● Development Request and Development Release Management:Enables customer-specific maintenance procedures and open integration with third-party products.

● Quality Management and Test Management:Reduce the time, cost, and risk associated with software changes.

● Support Packages and SAP Notes Implementation:Provide standardized software distribution and maintenance procedures.

6.1 Transport and Change Management

For transport and change management issues, the procedures of SAP NetWeaver apply.


6.2 Development Requests and Development Release Management

The standard procedures of SAP NetWeaver apply.

Operations Guide for SAP Risk Management 12.0 SP11Software Change Management PUBLIC 29




6.3 Quality Management and Test Management

You can use the SAP NetWeaver Development Infrastructure to learn about the various possibilities to test your software changes.

6.4 Support Packages and Patch Implementation

We recommend you implement Support Package Stacks (SP-STACKS), which are sets of Support Packages and patches for the respective product version that must be used in the given combination.

Read the corresponding Release Information Notes (RIN) before you apply any Support Packages or Patches of the selected SP-Stack.

The Release Information Note for SAP Risk Management 12.0 is available on the SAP Support Portal: 2623046.

The support packages for SAP Risk Management are available in the SAP Support Portal at https://support.sap.com/patches .

RecommendationFor information about the tools required for implementing patches, see the Technical Operations Manual for SAP NetWeaver at http://help.sap.com/netweaver SAP NetWeaver AS for ABAP 7.52 SAP NetWeaver Platform Technical Operations for SAP NetWeaver .


Software Change Management





http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fpatches

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fpatches


7 Troubleshooting

Use

SAP Risk Management is provided as an add-on component for SAP NetWeaver and uses the same troubleshooting tools as the SAP NetWeaver Application Server.

RecommendationFor more information about troubleshooting the SAP NetWeaver Application Server, see the Technical Operations Manual for SAP NetWeaver at http://help.sap.com/netweaver SAP NetWeaver AS for ABAP 7.52 SAP NetWeaver Platform Technical Operations for SAP NetWeaver .

Use the following component when reporting issues:

● GRC-RM for SAP Risk Management

Operations Guide for SAP Risk Management 12.0 SP11Troubleshooting PUBLIC 31


8 Configuring Remote Connection to SAP Support

SAP offers access to remote support and remote services. You have to set up a remote network connection to SAP.

RecommendationFor more information, see SAP Support Portal at https://support.sap.com/en/tools/connectivity-tools/remote-support.html .

8.1 Read Only Role

Use

NoteReferences to SAP Process Control and SAP Access Control only apply if you have implemented and licensed those applications in addition to SAP Risk Management.

For remote support from SAP, a support user must have read-only access to the support tools. Since these applications are built upon the SAP NetWeaver ABAP stack, a support user can use the SAP standard CSS remote support tool which is accessible through the SAPGUI or web browser.

Integration

The read-only roles are as follows:

● SAP_GRC_FN_DISPLAY for SAP Process Control and SAP Risk Management● SAP_GRAC_DISPLAY_ALL for SAP Access Control

32 PUBLICOperations Guide for SAP Risk Management 12.0 SP11Configuring Remote Connection to SAP Support

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Ftools%2Fconnectivity-tools%2Fremote-support.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Ftools%2Fconnectivity-tools%2Fremote-support.html

9 Appendix

Related Information

Categories of System Components for Backup and Restore [page 33]Related Information [page 35]

9.1 Categories of System Components for Backup and Restore

Categories of System Components

Category Properties Suggested Methods for Backup and Restore

Examples

I Only software, no configura-tion, or application data

No backup, new installation in case of a recovery

BDOC modeler

Initial software backup after installation and upgrade

Backup of log files

II Only software and configura-tion information, no application data

Backup after changes have been applied

SAP Gateway

No backup, new installation, and configuration in case of a recovery

Communication Station

Backup of log files SAP Business Connector, SAP IPC (2.0C)

III Only replicated application data, replication time is suffi-ciently small for a recovery

Data SAP IMS/Search

No data backup needed Engine

Backup of software, configu-ration, log files

SAP IPC (2.0B)

Operations Guide for SAP Risk Management 12.0 SP11Appendix PUBLIC 33

Categories of System Components


Examples

IV Only replicated application data, backup recommended because replication time is too long, data not managed by a DBMS

Data SAP IMS/Search

Application specific file system backup or

Engine

Multiple instances Web server


SAP IPC (2.0B)

V Only replicated application data, backup recommended because replication time is too long, data managed by a DBMS

Data SAP IPC (2.0B)

Database and log backup or Catalog Server

Multiple instances Web server


SAP IPC (2.0B)

Categories of Systems Components


Examples

VI Original application data, standalone system, data not managed by a DBMS

Data

Application specific file system backup

Backup of software, configu-ration and log files

Web Server

VII Original application data, standalone system, data managed by a DBMS, not based on SAP NetWeaver Application Server

Data

Database and log backup


none available

VIII Original application data, standalone system, based on SAP NetWeaver Application Server

Data

Database and log backup, application log backup (such as job logs in file system)


Standalone SAP

SAP ERP

none available


Appendix

Categories of Systems Components


Examples

IX Original application data, data exchange with other systems, data not managed by a DBMS

Data

Application specific file system backup, data consistency with other systems must be considered


none available

X Original application data, data exchange with other systems, data managed by a DBMS, not based on SAP NetWeaver Application Server

Data

Database and log backup, data consistency with other systems must be considered


SAP Live Cache

SAP Mobile

Workbench

XI Original application data, data exchange with other systems, based on SAP NetWeaver Application Server

Data

Database and log backup, application log backup (such as job logs in the system), data consistency with other systems must be considered


SAP ERP

SAP CRM

SAP APO

SAP NetWeaver Business Warehouse

9.2 Related Information

Product Product Page with Content

SAP Access Control https://help.sap.com/viewer/p/SAP_ACCESS_CONTROL

SAP Process Control https://help.sap.com/viewer/p/SAP_PROCESS_CONTROL

SAP Risk Management https://help.sap.com/viewer/p/SAP_RISK_MANAGEMENT

SAP NetWeaver https://help.sap.com/viewer/p/SAP_NETWEAVER

Operations Guide for SAP Risk Management 12.0 SP11Appendix PUBLIC 35

https://help.sap.com/viewer/p/SAP_ACCESS_CONTROL

https://help.sap.com/viewer/p/SAP_PROCESS_CONTROL

https://help.sap.com/viewer/p/SAP_RISK_MANAGEMENT

https://help.sap.com/viewer/p/SAP_NETWEAVER

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.


Important Disclaimers and Legal Information

Operations Guide for SAP Risk Management 12.0 SP11Important Disclaimers and Legal Information PUBLIC 37

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

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

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

operations guide for sap risk management 12.0 sp11

Documents