Master Guide

SAP ® BusinessObjects TM Risk Management 10.0

Target Audience
Èšž† Technology Consultants
Èšž† System Administrators

PUBLIC
Èšz¤ÄÄŽñx“´Ê9ÿpöDÖ”§ÎFGÞ©
þfl—lðÖ’¨ì~$h˛°|ñ£s·Üù
ÍO|êµÆöEKŠ•“§†ÛW
F
Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version on the SAP Service Marketplace at http://service.sap.com/
instguides → SAP BusinessObjects → SAP BusinessObjects Governance, Risk, Compliance (GRC) → Risk
Management → Risk Management Release 10.0.

The following table provides an overview of the most important document changes.
Version Date Description
1.0 2010-12-13 Initial Version
1.10 2011-01-31 Updated system landscape
1.20 2011-04-18 Added section 4.0 Content Lifecyle Management (CLM)
1.30 2011-06-28 Standardization

2/28 PUBLIC 2011-06-28

Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.1 Risk Management Planning Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.2 Further Useful Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2.3 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Risk Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Software Component Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Overall Implementation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3 Risk Management Business Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 4 Content Lifecycle Management (optional) . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.2 Software Component Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.4 Overall Implementation Sequence (ABAP 7.02) . . . . . . . . . . . . . . . . . . . . . . . . 17
4.5 Business Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 5 SAP BusinessObjects Risk Management Documentation . . . . . . . . . . . . . 19

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

2011-06-28 PUBLIC 3/28

This page is left blank for documents
that are printed on both sides.
1 Getting Started
1.1 About This Document

1 Getting Started

SAP BusinessObjects Risk Management 10.0 is a customizable software solution delivered as an add-on,
based on SAP NetWeaver 7.0 EHP 2 SP06. The Risk Management application enables an enterprise-wide
risk management process as mandated by legal requirements and recommended by best practice
management frameworks.

1.1 About This Document

This Master Guide is a central starting point for the technical implementation of Risk Management.
In this guide, you can find cross-scenario implementation information as well as scenario-specific
information. Use the Master Guide to obtain an overview of Risk Management, its software
components, and scenarios from a technical perspective.
If you want to know more about the major steps of the implementation sequence of Risk Management
10.0, see Overall Implementation Sequence [page 10].
This document consists of the following main sections:
+}²âù Getting Started
This section provides valuable information about using this document, and suggests further
documentation and related information (SAP Notes and links) crucial to the installation and add-
ons for Risk Management.
+}²âù Risk Management Overview
This section provides information about the technical system landscape, software components,
and implementation steps.
+}²âù Risk Management Business Scenarios
This section provides an overview of the main business scenarios provided by the system.
+}²âù Content Lifecycle Management
This section provides a general overview of Content Lifecycle Management.
+}²âù Risk Management Documentation
This section provides a general overview of related SAP documentation.
+}²âù Reference: The Main SAP Documentation Types
This section provides a general overview of the available SAP documentation.

NOTE

Current information about the implementation of SAP BusinessObjects Risk Management, and
the latest installation and configuration guides on SAP Marketplace at http://service.sap.com/

2011-06-28 PUBLIC 5/28

1 Getting Started
1.2 Related Information

instguides → SAP BusinessObjects → SAP BusinessObjects Governance, Risk, Compliance (GRC) → Risk
Management → Risk Management 10.0.

Constraints

This Master Guide primarily discusses the overall technical implementation of SAP BusinessObjects
Risk Management, rather than its subordinate components. This means that additional software
dependencies might exist without being mentioned explicitly in this document. You can find more
information on component-specific software dependencies in the corresponding installation guide.

CAUTION

Verify that you have the latest documents available on the SAP Service Marketplace before
beginning implementation.

1.2 Related Information

1.2.1 Risk Management Planning Information

For more information about planning topics not covered in this guide, see the following content on
SAP Service Marketplace:
Content
Latest versions of installation and upgrade guides
SAP Business Maps – information about applications/
solutions and business scenarios
General information about SAP BusinessObjects Risk
Management
Location on SAP Service Marketplace
http://service.sap.com/instguides → SAP
BusinessObjects → SAP BusinessObjects Governance, Risk,
Compliance (GRC) → Risk Management → Risk Management
10.0
http://service.sap.com/businessmaps
http://www.sap.com/solutions/
sapbusinessobjects/
large/governance-risk-compliance/
accessandauthorization/index.epx

Sizing, calculation of hardware requirements – such as http://service.sap.com/quicksizer

CPU, disk, and memory resource – with the Quick Sizer
tool
Released platforms and technology-related topics, http://service.sap.com/platforms
such as maintenance strategies and language support To access the Platform Availability Matrix directly,
enter http://service.sap.com/pam
Network security http://service.sap.com/securityguide

High Availability http://service.sap.com/ha

Performance http://service.sap.com/performance

Information about Support Package Stacks, latest http://service.sap.com/sp-stacks

software versions, and patch level requirements

6/28 PUBLIC 2011-06-28

1 Getting Started
1.2 Related Information

Content Location on SAP Service Marketplace

Information about Unicode technology http://service.sap.com/unicode@sap

1.2.2 Further Useful Links

The following table lists other useful links on the SAP Service Marketplace:
Content Location on SAP Service Marketplace
SAP Software Download Center (software download http://service.sap.com/swdc
and ordering software)
Information about creating error messages
SAP Message Wizard http://service.sap.com/mesage
Information about creating error messages
SAP Notes search http://service.sap.com/notes

SAP Online Knowledge Products (OKPs) role-specific http://service.sap.com/rkt

Learning Maps
SAP Release Notes http://service.sap.com/releasenotes → SAP
BusinessObjects → SAP BusinessObjects Goverance, Risk,
Compliance (GRC)→ SAP BusinessObjects GRC Risk Manager

1.2.3 Important SAP Notes

You must read the following SAP Notes before you start the installation or add-on upgrade. These SAP
Notes contain the most recent information on the installation of and add-on upgrades for SAP
BusinessObjects Risk Management 10.0, as well as corrections to the installation and upgrade
documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service
Marketplace at http://service.sap.com/notes.
SAP Note Number Title Description
1509999 Installing SAP GRC Shared Components 10.0 This note provides
information about installing
the software component
GRCFND_A version 1000.
1510000 Upgrading to SAP GRC Shared Components 10.0 This note provides
information about
upgrading to software
component GRCFND_A
version 1000.
1510001 Installing SAP POA Shared Business Components ABAP This note provides
100_702 information about installing
the software component
POASBC 100_702.
1510002 Installing SAP GRC Portal 10.0 This note provides
information about installing

2011-06-28 PUBLIC 7/28

1 Getting Started
1.2 Related Information

SAP Note Number Title Description

the software component
GRC_POR 1000.
1510053 Installing SAP GRC 10.0 Plug-in for Process Control This note provides
Installing Real Time Access (RTA) information about installing
SAP GRC 10.0 Plug-in for
Process Control.
1510055 Upgrading SAP ERP with GRC 10.0 Plug-in for Process This note provides
Control information about
Upgrading Real Time Access (RTA) upgrading SAP ERP with
GRC 10.0 Plug-in for Process
Control.
1503796 Release restrictions for GRC Process Control 10.0 This note provides
information about the
limitations and special
considerations in GRC
Process Control 10.0.
1536525 GRC Access/Process Control Upgrade — Add-on Handling This note provides upgrade
information.

8/28 PUBLIC 2011-06-28

 2 Risk Management Overview
2.1 System Landscape

2 Risk Management Overview

SAP BusinessObjects Risk Management enables you to proactively reduce risk by systematically
identifying, assessing, and controlling risks to prevent incidents and management failures.

2.1 System Landscape

The following graphic illustrates the GRC 10.0 Application landscape:

pŁ@©ÑýD¬}ð“ß:.›ÊH

RECOMMENDATION

As a best practice, we recommend implementing SAP GRC applications in three phases, with
separate systems for each:
pŁ@Oô4 Development
pŁ@Oô4 Testing
pŁ@Oô4 Production
For more information about three-tier landscapes, see the SAP NetWeaver Master Guide, located at
http://service.sap.com/instguides

2011-06-28 PUBLIC 9/28

2 Risk Management Overview
2.2 Software Component Matrix

CAUTION

We strongly recommend that you use a minimal system landscape for test and demo purposes
only. For performance, scalability, high availability, and security reasons, do not use a minimal
system landscape as your production landscape.

2.2 Software Component Matrix

Required or Optional Component Version Comment
Required NetWeaver 7.0, EHP 2, SP06, ABAP stack None
Mandatory NetWeaver 7.0, EHP 2, SP5 or higher, Java stack with usage types AS, EP, None
and BI

2.3 Overall Implementation Sequence

The following table describes the overall installation sequence for the Risk Management application.
For specific installation instructions, see the related installation documentation. For the latest
component version and patch level requirements, see the Important SAP Notes section in this Master
Guide.

NOTE

For more information, see the Product Availability Matrix posted on SAP Service Marketplace at
http://service.sap.com/pam..

To implement SAP BusinessObjects Risk Management 10.0:

Step Action
1. Install the back-end system.
2. Install the SAP BusinessObjects Risk Management 10.0 application.
3. Configure SAP BusinessObjects Risk Management 10.0..

10/28 PUBLIC 2011-06-28

3 Risk Management Business Scenario

3 Risk Management Business Scenario

NOTE

For more information about the implementation of the scenario, see Overall Implementation
Sequence [external document].

SAP BusinessObjects Risk Management 10.0 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 collaboratively identify these risks and to monitor them on a
continuous basis. Stakeholders and owners are provided with such tools as analytic dashboards for
greater visibility in mitigating risks in their areas of responsibility.
The business scenario consists of the following processes:
úLø^˘½ Risk Planning
Risk Planning includes the initial definition and assignment of roles and responsibilities, the setup
of the organizational hierarchy, and the definition of risk-relevant business activities (such as
processes, projects, or other company assets). Furthermore, it includes the development of risk
classifications to structure and report on risk assessment results, and the definition of a key risk
indicator framework to automate risk monitoring, thereby reducing effort.
Such structuring allows the implementation of risk management programs on a large scale,
enabling you to streamline risk planning and reduce duplicate efforts in your company’s different
organizational units.
The process includes the following steps:
1. Maintain business objectives
2. Maintain organizations
3. Assign user roles
4. Define key risk indicators
5. Maintain response catalog
6. Maintain risk catalog
7. Maintain opportunity catalog
8. Maintain activity hierarchy
úLø^˘½ Risk Identification
Risk Identification describes the process of identifying and collecting data about a company’s risks.
This includes documenting potential root causes, impacts, and relationships between risk events.
The process includes the following steps:
1. Define surveys and questions

2011-06-28 PUBLIC 11/28

3 Risk Management Business Scenario

2. Document activities
3. Propose risks
4. Document risks and opportunities
œk|IŠ? Risk Analysis
In the Risk Analysis process, you can qualitatively and/or quantitatively analyze the likelihood of
occurrence and the potential impacts of identified risks. This enables you to determine appropriate
responses to risks.
The process includes the following steps:
1. Conduct assessments
2. Build risk scenarios
3. Perform Monte Carlo simulations
œk|IŠ? Risk Response
In the Risk Response process, you document measures taken to manage the risk and its current
status. You also determine assessment and review cycles for the risks and responses.
The process includes the following steps:
1. Propose responses
2. Document responses and enhancement plans
œk|IŠ? Risk Monitoring
In the Risk Monitoring process, you analyze and report on your company's risk situation. This
step includes documenting incidents and losses for occurred risk events.
The process includes the following steps:
1. Monitor response and enhancement plans
2. Monitor key risk indicators
3. Review assessment status
4. Document incidents
5. Document issues
6. Report on risk situations

12/28 PUBLIC 2011-06-28

4 Content Lifecycle Management (optional)
4.1 Introduction

4 Content Lifecycle Management

(optional)

4.1 Introduction
The Content Lifecycle Management (CLM) component aims to support the management of partner
content, providing users with a consistent way to package, version-control, inspect, and import partner
content into their systems. It focuses on the capability to deliver content from vendors’ landscapes to
customers’ landscapes and does not provide means to transport content within one single landscape.
The latter capability is already provided by the ABAP transport system.
CLM is available on ABAP 7.3 and ABAP 7.02.
CLM is delivered as a single software component. There are different versions of this software
component available, depending on the version of the target platform.

4.2 Software Component Requirements

Business Scenario
Content Lifecycle Management
containing two business processes:
Providing Content and Consuming
Content
Software Unit Mandatory or Optional
POASBC (POA Shared Business Components) Mandatory
Version: POA_SBC_100_702

4.3 System Landscape

Content Lifecycle Management (CLM) is a software component with its own user interface,
communicating with one, or more managed applications. There are different landscape setups, based
on two key usage characteristics:
¡ÝŽ�Öä Single or Multi Application System management
¡ÝŽ�Öä Standalone or Integrated Installation
Version
Standalone Integrated
Number of Application One If CLM is used to manage If CLM is used to manage
Systems to be Managed application content application content
residing on a different residing on a single system,
system, the landscape the landscape depicted in
depicted in figure 1 can be figure 2 can be applied,
applied, where CLM is where CLM is installed as

2011-06-28 PUBLIC 13/28

4 Content Lifecycle Management (optional)
4.3 System Landscape
Version
Standalone
installed standalone as an
add-on to the NetWeaver
platform. In this case, CLM
can communicate with
the application system
using an RFC connection.
This landscape model can
be used if you do not want
to interfere with an
existing running
application system and its
associated technical
resources.
See figure 1: Standalone +
one system
Multiple If CLM is used to manage
application content
residing in multiple
systems on the landscape,
the deployment landscape
scenario depicted in figure
3 can be applied. In this
landscape model, CLM is
installed standalone as an
add-on to the NetWeaver
platform.
This landscape can be used
when you want to have
only CLM system as a
central box that can
communicate with other
managed application
systems.
See figure 3: Standalone +
multiple systems
14/28 PUBLIC
Integrated
an add-on to the same
managed application
system.
When you install a
managed application on
your system, you can also
install the CLM add-on on
the same system. In this
case, both the application
and CLM can be operated
from a single system
without an RFC
connection.
See figure 2: Integrated +
one system
If CLM is used to manage
application content
residing in multiple
systems on the landscape,
the complex deployment
landscape scenario
depicted in figure 4 can be
applied. In this landscape
model, CLM is installed as
an add-on to one of the
managed application
systems.
This landscape mode
could fit use cases where
one application system is
frequently used with CLM
for managing the its
content lifecycle, while
other participating
application systems
interact with CLM only a
few times.
See figure 4: Integrated +
multiple systems
2011-06-28
4 Content Lifecycle Management (optional)
4.3 System Landscape

y/Aªåk
ô¶>mgc°ł! `¸¬¹6Figure 1: Standalone + One System

y/Aªåk
ô¶>mgc°ł! a¸¬¹6Figure 2: Integrated + One System

y/Aªåk
ô¶>mgc°ł! f¸¬¹6Figure 3: Standalone + Multiple Systems

2011-06-28 PUBLIC 15/28

4 Content Lifecycle Management (optional)
4.3 System Landscape

É“aÖ
äá7˘Éıwt±MŁcE(sFigure 4: Integrated + Multiple Systems

Communication with managed applications happens via function calls through RFC destinations of
SAP NetWeaver Application Server ABAP. Such communication channels can be configured for remote
communication. This allows different actual landscapes to be formed.

NOTE

A landscape designed according to the above principles can be used for both providing content
and consuming content. In case of separate Content Provisioning (vendor) and Content
Consumption (customer) processes; a typical landscape can look as follows:

É“aÖ
äá7˘Éıwt±MŒcE

16/28 PUBLIC 2011-06-28

4 Content Lifecycle Management (optional)
4.4 Overall Implementation Sequence (ABAP 7.02)

Alternatively, these two processes can share the same landscape (with both extraction and
deployment being handled in the same CLM system. It must be verified during the design of the
landscape that both business processes can be executed in such a dual-purpose landscape.
For example: Separate authorizations/users must be associated with separate application systems
so that content deployment is not accidentally performed on the system that is restricted for
content extraction.

4.4 Overall Implementation Sequence (ABAP 7.02)

The following table provides a high-level overview of the installation sequence for Content Lifecycle
Management (CLM).
Step Action Remarks/Subsequent Steps
1 Installation of If CLM is being installed along with the application, the minimum platform
software component prerequisites are met during the installation of the application; however, if you
POASBC — software are installing CLM as an add-on to a separate server, make sure that NetWeaver
component version 7.02 for ABAP is already installed.
POA_SBC_100_702 For more information, see the installation guide for SAP NetWeaver on SAP Service
Marketplace at http://service.sap.com/instguides.
2 Post-installation of For details about the installation and configuration steps, see the installation
software component information.

NOTE

Specifying a unique authoring namespace is not mandatory if CLM is only used for consuming
content.

CAUTION

If CLM is installed for the dual purpose of consuming content and providing content, the rules
for providing content apply to the formulation of the vendor namespace. It must be globally
unique, as supplied by SAP. For more information about the service for namespace issuing provided
by SAP, see SAP Service Marketplace at http://service.sap.com/namespaces.

4.5 Business Scenario

You can use Content Lifecycle Management to manage the creation and distribution of application
content. This is particularly useful if you want to create content packages for a specific application that
are going to be shared with or reused by other instances of the same application. This applies even if
they are running in a different system landscape. For example, consulting companies can create content
packages for an application and distribute this content to their customers. Those customers can merge
this new content with the content currently used in the application.
Content Lifecycle Management covers extraction of content from applications, creation of content
packages for content sharing across system landscapes, and editing of extracted content in a spreadsheet

2011-06-28 PUBLIC 17/28

4 Content Lifecycle Management (optional)
4.5 Business Scenario

application. It also includes detection of differences between content groups and deployment of content
to an application.
The Content Lifecycle Management business scenario is divided into two business processes:
±
·%˚n Providing Content: Used by vendors and content authors to provide and distribute application
content to their customers
±
·%˚n Consuming Content: Customers deploy and use vendor content in their applications
For more information about the business scenario and business processes, refer to the Solution Manager
Content documentation.
For technical system landscape, software units, and implementation sequence, refer to sections in
previous chapter of this guide.

18/28 PUBLIC 2011-06-28

5 SAP BusinessObjects Risk Management Documentation

5 SAP BusinessObjects Risk

Management Documentation

SAPBusinessObjectsProcessControl 10.0, SAPBusinessObjectsRiskManagement 10.0, and SAP

BusinessObjects Access Control 10.0 have a shared install instance and share some of the same
documentation.
Documentation Location
SAP BusinessObjects http://service.sap.com/instguides → SAP BusinessObjects → SAP BusinessObjects
Access Control, Governance, Risk, Compliance (GRC) → SAP BusinessObjects Access Control 10.0, Process Control 10.0,
Process Control and or Risk Management 10.0
Risk Management
Installation Guide
SAP BusinessObjects http://service.sap.com/instguides → SAP BusinessObjects → SAP BusinessObjects
Access Control, Governance, Risk, Compliance (GRC) → SAP BusinessObjects Access Control 10.0, Process Control 10.0,
Process Control and or Risk Management 10.0→ SAP BusinessObjects Risk Management 3.0
Risk Management
Security Guide
SAP BusinessObjects http://service.sap.com/instguides → SAP BusinessObjects → SAP BusinessObjects
Access Control, Governance, Risk, Compliance (GRC) → SAP BusinessObjects Access Control 10.0, Process Control 10.0,
Process Control and or Risk Management 10.0
Risk Management
Operations Guide

Documentation Location
SAP BusinessObjects http://service.sap.com/instguides → SAP BusinessObjects → SAP BusinessObjects
Upgrade Guide Governance, Risk, Compliance (GRC) → SAP BusinessObjects Access Control or Process Control→
SAP BusinessObjects Access Control 10.0 or Process Control 10.0
SAP BusinessObjects On SAP Help Portal at http://help.sap.com
Application Help

2011-06-28 PUBLIC 19/28

This page is left blank for documents
that are printed on both sides.
A Reference
A.1 The Main SAP Documentation Types

A Reference

A.1 The Main SAP Documentation Types

The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software.

Cross-Phase Documentation

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, as

well as many glossary entries in English and German.
‘Ó©ô½u Target group:
‘Ó©ô½ˆ Relevant for all target groups
‘Ó©ô½u Current version:
‘Ó©ô½ˆ On SAP Help Portal at http://help.sap.com Glossary
‘Ó©ô½ˆ In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes.
‘Ó©ô½u Target group:
‘Ó©ô½ˆ Consultants
‘Ó©ô½ˆ System administrators
‘Ó©ô½ˆ Project teams for implementations or upgrades
‘Ó©ô½u Current version:
‘Ó©ô½ˆ On SAP Help Portal at http://help.sap.com (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels. A collective security guide is available for SAP NetWeaver. This document contains
general guidelines and suggestions. SAP applications have a security guide of their own.
‘Ó©ô½u Target group:
‘Ó©ô½ˆ System administrators
‘Ó©ô½ˆ Technology consultants
‘Ó©ô½ˆ Solution consultants
‘Ó©ô½u Current version:
‘Ó©ô½ˆ On SAP Service Marketplace at http://service.sap.com/securityguide

Implementation

The master guide is the starting point for implementing an SAP solution. It lists the required installable
units for each business or IT scenario. It provides scenario-specific descriptions of preparation,

2011-06-28 PUBLIC 21/28

A Reference
A.1 The Main SAP Documentation Types

execution, and follow-up of an implementation. It also provides references to other documents, such
as installation guides, the technical infrastructure guide and SAP Notes.
a´¿´2 Target group:
a´¿´] Technology consultants
a´¿´] Project teams for implementations
a´¿´2 Current version:
a´¿´] On SAP Service Marketplace at http://service.sap.com/instguides
The installation guide describes the technical implementation of an installable unit, taking into
account the combinations of operating systems and databases. It does not describe any business-related
configuration.
a´¿´2 Target group:
a´¿´] Technology consultants
a´¿´] Project teams for implementations
a´¿´2 Current version:
a´¿´] On SAP Service Marketplace at http://service.sap.com/instguides
Configuration Documentation in SAP Solution Manager – SAP Solution Manager is a life-cycle
platform. One of its main functions is the configuration of business scenarios, business processes, and
implementable steps. It contains Customizing activities, transactions, and so on, as well as
documentation.
a´¿´2 Target group:
a´¿´] Technology consultants
a´¿´] Solution consultants
a´¿´] Project teams for implementations
a´¿´2 Current version:
a´¿´] In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The
Customizing activities and their documentation are structured from a functional perspective. (In order
to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager,
which refers to the relevant Customizing activities in the individual SAP systems, is used.)
a´¿´2 Target group:
a´¿´] Solution consultants
a´¿´] Project teams for implementations or upgrades
a´¿´2 Current version:
a´¿´] In the SAP menu of the SAP system under Tools Customizing IMG

Production Operation

The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver, and precedes the application operations guides of SAP Business Suite. The manual refers

22/28 PUBLIC 2011-06-28

A Reference
A.1 The Main SAP Documentation Types

users to the tools and documentation that are needed to carry out various tasks, such as monitoring,
backup/restore, master data maintenance, transports, and tests.
@Ł@a¹# Target group:
@Ł@a¹L System administrators
@Ł@a¹# Current version:
@Ł@a¹L On SAP Service Marketplace at http://service.sap.com/instguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed. It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks.
@Ł@a¹# Target group:
@Ł@a¹L System administrators
@Ł@a¹L Technology consultants
@Ł@a¹L Solution consultants
@Ł@a¹# Current version:
@Ł@a¹L On SAP Service Marketplace at http://service.sap.com/instguides

Upgrade

The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of
an upgrade. It also refers to other documents, such as upgrade guides and SAP Notes.
@Ł@a¹# Target group:
@Ł@a¹L Technology consultants
@Ł@a¹L Project teams for upgrades
@Ł@a¹# Current version:
@Ł@a¹L On SAP Service Marketplace at http://service.sap.com/instguides
The upgrade guide describes the technical upgrade of an installable unit, taking into account the
combinations of operating systems and databases. It does not describe any business-related
configuration.
@Ł@a¹# Target group:
@Ł@a¹L Technology consultants
@Ł@a¹L Project teams for upgrades
@Ł@a¹# Current version:
@Ł@a¹L On SAP Service Marketplace at http://service.sap.com/instguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release. Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG).
@Ł@a¹# Target group:

2011-06-28 PUBLIC 23/28

A Reference
A.1 The Main SAP Documentation Types

l-3#⁄6 Consultants
l-3#⁄6 Project teams for upgrades
l-3#⁄Y Current version:
l-3#⁄6 On SAP Service Marketplace at http://service.sap.com/releasenotes
l-3#⁄6 In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)

24/28 PUBLIC 2011-06-28

Typographic Conventions

Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
Example Arrows separating the parts of a navigation path, for example, menu options
Example
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example $flüǬ Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
$flüǬ Cross-references to other documentation or published works
Example $flüǬ Output on the screen following a user action, for example, messages
$flüǬ Source code or syntax quoted directly from a program
$flüǬ 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 names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard

2011-06-28 PUBLIC 25/28

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,
z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented
by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, and other SAP products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other
countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius,
and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects Software Ltd. in the United States and in other countries.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not
be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.

Disclaimer

Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/instguides

26/28 PUBLIC 2011-06-28

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2011 SAP AG. All rights reserved.

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