SAP Solution Manager

(1)

©SAP AG 2005

-Solution Monitoring

SAP Solution Manager Product Management,

SAP AG

(2)

©SAP AG 2005

Concept

Functionality

What is SAP Solution Manager

(3)

©SAP AG 2005

SAP

Development

SAP

Custom Code

Development

SAP

Consulting

SAP

Education

SAP

Hosting

SAP

Active Global

Support

Standardized & integrated application management

SAP Solution Manager – Value Proposition

SAP Solution Manager

The support hub and the gateway to SAP

Implementation of SAP solutions

Customer

Collaboration

Solution monitoring

Service desk

Change request management

Delivery of SAP services

Diagnostics

Upgrade of SAP solutions

Flexibility

Transparency

Control

Efficiency

OPERATE IMPLEMENT OPTIMIZE

Core

Business

Process

Objective: Present the SAP Solution Manager value proposition

________________________________________________________________________

On the right-hand two-thirds of the slide you have a gray box representing the customer’s environment.

Their IT landscape contains the applications we’d expect to see – some SAP and some not. In the center

of this landscape we have the core business processes that drive the company, and the IT group’s charter

– to implement, operate, and continually optimize these processes, as well as the applications. The goals

of the CIO are represented in black in this box – efficiency, transparency, control, and flexibility. (These are

the four core value props that SAP Solution Manager provides) That is, if a CIO could maximize these four

goals then the chances of success in their mission would be significantly increased. Moving to the left, the

customer’s IT landscape is connected to the SAP Solution Manager.

SAP Solution Manager is a unique solution stack which enables several of its integrated business

processes to seamlessly interact with the customer’s IT landscape (change management, service desk,

etc). These business processes are core function within SAP Solution Manager and replace the customer’s

need to purchase, implement, and maintain separate software and hardware solutions that provide these

functions. This is one very significant benefit that SAP Solution Manager brings – the ability to replace

several un-integrated tools with a single product which provides seamless integration, a single user

interface (for ease of use), and which comes at no extra cost as a part of their SAP Standard Support. The

importance of SAP Solution Manager in both cost and efficiency terms cannot be over-stated.

However, there’s an additional benefit with SAP Solution Manager, and that is its role as a gateway to

SAP’s Active Global Support (AGS) organization and the network of over 12,000 professionals we can call

upon to assist our customers. Specifically (on the far left-hand of the slide), AGS is able to interact with a

number of SAP organizations to ensure that our customers receive the right assistance at the right time.

(4)

©SAP AG 2005

Change Request

Management

Standard usage

Maintenance processes

SAP Solution Manager Scenarios

Service Desk

Standard usage

coupled with

3rd-party tool

Corporate functionality

Solution Manager

Diagnostics

Solution Monitoring

System monitoring

EarlyWatch Alert

Service level reporting

Business prozess monitoring

Central system administration

Upgrade of

SAP solutions

Classical upgrade

E-learning mgmt.

Test management

Implementierung

of SAP solutions

Standard usage

Global rollout

Customizing sync.

E-Learning mgmt.

Test management

CORE

BUSINESS

PROCESS

Delivery of

SAP services

On-site / remote delivery

Expertise on demand

SAP Safeguarding

(5)

©SAP AG 2005

The More Transparent the Solution, the More You Benefit!

All training

information

All maintenance

activities

All service planning,

deliver ad follow-up

information

All business processes

All systems

All monitoring data

All service level information

All test information

All customer

developments and

functional enhancements

The entire documentation

All change

information

All incident and

problem information

SAP

SOLUTION

MANAGER

(6)

©SAP AG 2005

Role of Solution Manager in Lifecycle Management

Application Management

Maintenance strategy, processes, and projects

Continuous improvement projects

Software Change Management

Development and enhancement projects

Deployment projects

NetWeaver Lifecycle Management

SAP NetWeaver Administration Tools + Software Logistics

Daily system administration and monitoring

Configuration

Initial Setup

Software Maintenance Management

Business Content Lifecycle

(7)

©SAP AG 2005

Concept

Functionality

(8)

©SAP AG 2005

SAP Solution Manager - Architecture

Solution

Testing

E-Learning

Management

Global Rollout

Process Templates BETRIEB IMPLEMENT. OPTIMIEREN Business-process

(9)

©SAP AG 2005

Proactive Monitoring vs. Reactive Monitoring

Why Solution Monitoring?

Monitoring should be done to detect the deficiencies as early as possible in

order to ensure the

correctness and security of the business processes

raise the

availability and performance of the system

.

Proactive Monitoring

Proactive Monitoring tries to

avoid critical situations

before the occur.

E.g.: Maintenance of performance alert thresholds

E.g.: Trend analysis (e.g. performance values and hardware capacity)

-> To be reminded of the necessary monitoring tasks, interactive work lists are

needed (Alert Graphic)

Reactive Monitoring

Reactive Monitoring tries to

notify the administrators in critical situations

as

soon as possible

E.g.: error handling procedures and escalation paths

-> Via automatic notification mechanisms

(10)

©SAP AG 2005

Automatic Monitoring vs. Expert Monitoring

Automatic Monitoring

Automatic Monitoring is using

predefined Key Performance

Indicators (KPI)

in order to notice deviations as early as possible.

E.g.: Autoreaction methods with CCMS as infrastructure

E.g.: KPI monitoring and reporting with ratings in case of problems

-> Definition of Key Performance Indicators and their thresholds

needed

Manual Expert Monitoring

Expert Monitoring

is manual work

.

Identify issues that are not captured via alert monitoring.

Expert Monitors should give hints for resolution of identified

problems or are the tools for resolution of problems.

E.g.: Link to expert monitors in satellite systems

Identify problems that are based on long-running trends.

(11)

©SAP AG 2005

Concept

Functionality

(12)

©SAP AG 2005

The “Old” Monitoring Concept

“Old” concept is not extendable

to the new world

Increasing number of

components (R/3 + CRM +

3rd-party + ITS + …)

Many new components have

their own individual

administration and monitoring

tools

Exploding costs for training,

implementation and operations

SAP Service

Marketplace

SAP Active

Global Support

CUS

SCM

CUS

FVS

4.6C

PLM

System

administrator

IT organizations are subject to increasing fragmentation

Ever more and more complex business processes are being implemented

"Best-of-Breed" solutions

More components, larger components, more complex components

IT experts, training concept

Available know-how on (employment) market

Cost pressures

User requirements

Less training

Intranet/Internet users

Employee Self Services, Internet Sales and Service

Demand 24 hour/day, 365 days/year

A new monitoring concept is required!

(13)

©SAP AG 2005

Solutions in SAP Solution Manager

Solutions are groups of related systems. The design of solution landscapes

can be related to the SAP Solution Manager functionality you want to use or

to user groups which should have access, e.g. landscapes for

reporting (EarlyWatch Alert, SL, Service and Availability Reporting),

joint administration and real-time monitoring (e.g. System Monitoring and

Central System Administration)

management of core business processes and related components (BPM) so

that customers of an outsourcer have access to their business process related

data

Individual and flexible assignment of systems within solutions

Solution 2

(BPM Customer 1)

Solution 1

(EWA)

Solution 3

(BPM Customer2)

CRM ERP BI SCM R/3 CRM ERP BI ERP BI

Solutions

You specify solutions, to use the SAP Solution Manager effectively. A solution contains systems

in your system landscape, which you assign according to certain criteria, for example:

It contains all systems used in the production processing in your system landscape, i.e. on which one or

more of your most important business processes run. You can proactively monitor the business

processes, business process steps, and interfaces of these systems (e.g. all production systems).

It has a restricted view of the systems in your system landscape, e.g. for a business area.

The definition of solutions allows you to monitor all systems in a solution, or all business

processes which run in the systems.

Specify the solution scope in the Solution Directory, for example:

which system components they use, or which business processes and business process steps you want

to monitor in the Solution Monitoring

for which systems the EarlyWatch Alert data is to be collected.

(14)

©SAP AG 2005

The “New” Concept: Solution Monitoring

SAP Service

Marketplace

Central

Monitoring

Instance

SAP Active

Global

Support

CUS

SCM

CUS

FVS

4.6C

PLM

System

administrator

Solution Landscape

(e.g. to monitor core

business processes or to

report system KPIs)

Solution Monitoring “Mission Statement”

Provide central point of access to all data relevant for monitoring

Provide a disciplined, proactive methodology and procedures used to ensure that adequate levels of

service are delivered to all IT users in accordance with business priorities and at acceptable cost

Solution Monitoring is

Business process oriented

Software solution landscape oriented

Configurable, linked to expert analysis and administration tools

Open and extendible: Covers all software components in the IT landscape, from SAP R/3 to “new” SAP

components to non-SAP components

(15)

©SAP AG 2005

Solution Monitoring and Reporting in the SAP Solution

Manager

Early Watch Alert and Service Level Reporting

Weekly evaluation of system status and performance

Weekly or monthly reporting on SLAs for the involved

systems and business processes

System Monitoring and Administration

Technical real-time monitoring of system

components based on the

CCMS

infrastructure

System-related tasks with integrated and

automated log

Business Process and Interface Monitoring

Real-time monitoring of

business

processes

based on the

CCMS

infrastructure

Covers all technical and business

application-specific functions required for a smooth and

reliable flow of business processes

(16)

©SAP AG 2005

SAP Solution

Manager

Satellite

Systems

System Monitoring

Continous Monitoring:

Service Data Download

(SDCC)

Continous Monitoring:

Service Data Download

(SDCC)

Real-time Monitoring:

CCMS Monitoring

Infrastructure (RZ20)

Real-time Monitoring:

CCMS Monitoring

Infrastructure (RZ20)

Solution Monitoring and Reporting – Data Collection

SAP

EarlyWatch

Alerts

Business Processes

Detailed

Reporting

Critical Alert

Situations:

Business Process

Monitoring

(17)

©SAP AG 2005

Integration of 3rd-Party Tools

CCMS Monitoring

Infrastructure (“RZ20)

Monitoring

Infrastructure

Solution

Landscape

Monitoring

Agent

3

rd

-Party

Components

Report Alerts

3

rd

-Party

System

Management

Console

Trigger console

in case of an alert

(SAPConnect;

SNMP; XML)

Detailed Analysis

with 3

rd

-party tools

Solution

Monitoring

(18)

©SAP AG 2005

Solution Monitoring – Benefits Overview

Central point of access to all monitoring information

Reduce administration effort

Central monitoring of complete solution

Cover inter-system dependencies

Avoid critical situations by proactive monitoring

Detect issues before they occur

Improve availability your solution

Fast issue resolution

Automatic notification in critical situations

Openness

Investment protection for your existing landscape

Integration of 3rd-party systems

Costs

(19)

©SAP AG 2005

Concept

Functionality

(20)

©SAP AG 2005

Functionality

Concept

Solution Monitoring - Introduction

System Monitoring / Central System Administration

Business Process Management and Monitoring

(21)

System Monitoring in the SAP Solution Manager

The system monitoring in the SAP Solution Manager, uses the Computing Center Management

System (CCMS) (transaction RZ20) architecture. This means that system alerts which occur in

the local CCMS, are passed to the SAP Solution Manager via RFC connections between the

SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in

Sessions. You can also handle the alerts centrally, without having to go to the local CCMS of the

satellite systems.

You can see the alerts from several systems in a solution landscape in the SAP Solution

Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager

satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP

systems in a central CCMS (CEN) of a satellite system.

©SAP AG 2005

System Monitoring

Goals

Financial savings due to reduced probability of system downtime or

business process interruptions and overtime costs

Improvement in motivation of IT staff

Higher end-user satisfaction

Realization within SAP Solution Manager

System monitoring of core components to detect critical situations as

early as possible

Support operators working with SAP solutions

System monitoring and Central System Administration complement

each other

(22)

©SAP AG 2005

System Monitoring - Workflow

Satellite

Systems

SAP Solution

Manager

Collect Data

Get CCMS

Alerts

Navigate directly

into Satellite System

2

Root cause

analysis

Check CCMS

Expert Monitors

and solve

Problem

1

Agents send Alert

Data

Display and

dispatch Alerts

(e-mail; SMS;

Support Desk

message)

The technology behind System Monitoring is based on so called agents.

Those collect data more efficient, collect additional data and enable a push technology for

delivering alerts.

There are three basic agents:

SAPCCMSR: Monitors components without any active SAP basis instance. This can be used on servers

like ITS, Portals, and other servers that do not run an SAP basis instance. There does not have to be a

SAP product on the server for this to be installed. Detailed operating system data by help of SAPOsCol

which has also to be installed on the server.

SAPCCM4X: Transfers CCMS alert monitoring data to the central system without using a dialog work

process. This should be installed on systems that use a SAP basis system above release 4.X. This also

includes the 6.X basis releases.

SAPCCM3X: Connects SAP Systems 3.X to a central monitoring architecture delivering dispatcher‘s

performance data.

There are also additional agents that monitor specific technologies...such as Java, etc.

Additional information you can find under: www.service.sap.com/systemmanagement >> System

Monitoring and Alert Management >> Media Library

(23)

©SAP AG 2005

System Monitoring – Workflow

System monitoring of core components to

detect critical situations as early as possible

Support administrators working with new

SAP products

System monitoring and Central System

Administration complement each other

Expert monitors

directly linked in

satellite systems

Alert graphics

System-related

tasks with

integrated and

automated log

(24)

©SAP AG 2005

Solution Overview - Entry Screen

Solution

Overview

Automated

refresh

QuickLink:

solutionmanager

Summary of alerts

with navigation to

alert graphic in

solution

Navigate to open

tasks in solution

(25)

©SAP AG 2005

System Monitoring - Graphic

Display of all monitoring features

under the header Solution

Monitoring

Graphical

display of

components

and alerts

System monitoring

alerts and CSA

tasks in one

graphic

(26)

©SAP AG 2005

Solution Monitoring - Alert List

Alternative Display of

values as alert list

ALV standard selection and

maintenance possibilities

Switch between Current and

Open Alerts (Alert History)

(27)

©SAP AG 2005

Setup System Monitoring –

Centralized Maintenance of Alerts and Thresholds

Copy Customizing

between components

Centrailized maintenance of

autoreaction methods

Preselected and

activated CCMS alerts

Centralized maintenance of alerts and

thresholds (changes are automatically

transferred to local CCMS)

(28)

©SAP AG 2005

Preselected and Activated CCMS Alerts

Performance Alerts of Instance

Dialog Alerts

Response time

DB request time

Memory Mngt and Buffer Alerts

ES Peak

Single record buffer

Generic key buffer

Setup Monitoring for Server

CPU 5MinLoadAverage

Paging out

Database

Administrating DB

Space Management

(29)

The technology behind System Monitoring is based on so called agents.

Those collect data more efficient, collect additional data and enable a push technology for

delivering alerts.

There are three basic agents:

SAPCCMSR: Monitors components without any active SAP basis instance. This can be used on servers

like ITS, Portals, and other servers that do not run an SAP basis instance. There does not have to be a

SAP product on the server for this to be installed. Detailed operating system data by help of SAPOsCol

which has also to be installed on the server.

SAPCCM4X: Transfers CCMS alert monitoring data to the central system without using a dialog work

process. This should be installed on systems that use a SAP basis system above release 4.X. This also

includes the 6.X basis releases.

SAPCCM3X: Connects SAP Systems 3.X to a central monitoring architecture delivering dispatcher‘s

performance data.

There are also additional agents that monitor specific technologies...such as Java, etc.

Additional information you can find under: www.service.sap.com/systemmanagement >> System

Monitoring and Alert Management >> Media Library

©SAP AG 2005

Central System Administration

Goals

Financial savings due to reduced administration effort

Improvement in motivation of IT staff

Documentation and Reporting on system maintenance tasks

Realization within SAP Solution Manager

manages tasks for the systems in your solution, centrally

preconfigured view and logical collection of administration tasks

generated component-specific administration tasks, divided into

logical areas, depending on the SAP system types

(30)

©SAP AG 2005

Central System Administration (CSA) - Workflow

Satellite

Systems

SAP

Solution

Manager

Expert

Monitor

1

Check System

Get Task in

Graphic

Confirm Task

and get Log

Entry

2

(31)

©SAP AG 2005

Central System Administration – Task Handling

Create task logs

Set-up and

perform tasks

Monitor task plans

and status

(32)

©SAP AG 2005

Functionality

Concept

Solution Monitoring - Introduction

System Monitoring / Central System Administration

Business Process Management and Monitoring

(33)

©SAP AG 2005

Why Business Process Management

An overall concept for Business Process Management gets more

and more important

Complex business processes

that are distributed across various

systems and software components in a complex solution landscape

Different and

various application error logs

on different software

components have to be monitored for a distributed business process

The need of a particular

system component

for a business process is

not necessarily obvious and must be documented

Data transfer

between different systems using various interface

techniques must be monitored

Business Process Management means to answer questions like

Who is responsible and checks for background job scheduling?

Who monitors proactively and verifies throughput, performance, and response times?

Who monitors and checks for update errors and application logs?

Who monitors the interfaces?

(34)

©SAP AG 2005

Why Solution Management

Solution Management gets more and more important

Complex Solutions with distributed System Landscapes

Past:

Fully integrated applications

in an SAP R/2 or R/3 System with a defined number of

interfaces to legacy system(s), tools for day-to-day operation were included in and provided

by the software (Software Logistics (TMS), System Monitoring (ST** Transactions, CCMS

Alert Monitor), application error logs, user management etc.)

Present: Internet era with

different SAP and non-SAP software components

for CRM, B2B

(SRM, EBP), B2C, SCM (APO), BW including various interfaces and different technical

components (more complex technologies)

Why SAP Solution Manager

Software that serves as a

central tool

for system and business process operation

for all systems and business processes within your Solution Landscape

Implementation

and

Operation

is covered, including

documentation

and

monitoring

of all systems and business processes (and EarlyWatch Alert and

Service Level Reporting)

Better supportability

of your solution by SAP’s Active Global Support in case of

problems and critical situations

(35)

©SAP AG 2005

Business Process Monitoring

Definition of Business Process Monitoring

Business Process Monitoring is the

proactive

and

process-oriented

monitoring of a company’s core business processes

It includes the observation of all

technical

and

application-related

functions that are required for a smooth and reliable

flow of the core business processes

It comprises detailed procedures for

error handling

and

problem resolution

and precise definition of

contact persons

(36)

©SAP AG 2005

Monitoring with Business Process Monitoring (BPM)

SAP

Solution Manager

Customer

SAP Support

SAP

Log on to Solution

Manager

3

Send

Support Message via

Support Desk to SAP

1

Transfer Monitoring Data

Satellite

System

BPM in SAP

Solution

Manager

Collect Data

Check Support Message

SAP: Check Alert and

Configuration,

Solve Problem,

Give

Recommen-dation

Cust.: Close Support

Message

4

5

Analyze and Fix

Problem

Tool: Alert Display,

Trigger Workflow

Cust.: Check Alert,

Create Support

Message

2

Implement

Recommendations

Contact Customer

Tool = as customized in SAP Solution Manager, automatically done by tool Cust. = to be done by customer

(37)

©SAP AG 2005

Solution Manager

Solution Landscape

Infrastructure for BPM in the SAP Solution Manager

Monitoring Graphic

Monitoring Session

Monitoring Infrastructure

CCMS Monitoring

Infrastructure

Solution Manager

Monitoring Engine

CCMS Monitoring

Infrastructure

SAP R/3

data

collectors

APO

data

collectors

BW

data

collectors

CRM

data

collectors

EBP

data

collectors

(38)

©SAP AG 2005

Monitoring tasks, Error Handling

and Escalation Paths for the

monitoring employee

Integration with BPM in SAP Solution Manager

Business Process Monitoring

Automatic Email

reporting an alert

Process Description from

Implementation Project in

the SAP Solution Manager

Integration with System Monitoring

(Status of Hardware, Software and

Business Processes in one screen)

Direct link to analysis

transactions in satellite system

Service Desk message

in case of alert

(automatic or manual)

(39)

©SAP AG 2005

Display Business

Process Alerts

Components and

related business

processes

(40)

©SAP AG 2005

Business process step

alert list

Display Current Alerts, Alert

History and detailed information

(41)

©SAP AG 2005

Direct navigation to

analysis method in

satellite systems

Business Process

Monitoring session

Creation of support

notifications, workflow

trigger, alert confirmation

Documented

error handling procedures

and contact persons

(42)

©SAP AG 2005

BPM Functionalities in the SAP Solution Manager

What can be monitored by Business Process Monitoring ?

All alert

information via

CCMS alert

infrastructure

Customer exit in

Application

Monitoring

infrastructure

ALE / IDoc

alert

monitoring

qRFC alert

monitoring

Error logs (e.g.

SD Duelist, APO

Planning)

MRP Runtime

statistics

EBP Process

Alerts

etc

Background jobs

Performance of dialog

transactions (Transaction

code and function code

level)

Transaction-specific

Update errors

Document volume based

on SAP Table statistics

Application Log (SLG1)

Customer

specific objects

Interface

objects

Application

specific objects

Cross Application

objects

(43)

©SAP AG 2005

E-learning

SAP Service Marketplace

www.service.sap.com/solutionmanager

www.service.sap.com/rkt-solman

(role-based, free of charge learning maps)

www.service.sap.com/monitoring

(CCMS, GRMG, autoreaction, agents)

www.service.sap.com/bpm

(Business Process Management, setup guide)

www.service.sap.com/diagnostics

Training

Support Academy/SAP Education

USMP10

–

SAP Solution Manager Concept & Strategy

USMX20 –

Installation &

Technical Configuration of SAP Solution Manager Infrastructure

USMA30 – System Administration with SAP Solution Manager

USCP60 – Business Process Management

USMF50 –

SAP Solution Manager Implementation of

Service Desk Functions

USMF55 – Change Request Management with SAP Solution Manager

SMI310 – SAP Solution Manager Implementation Tools

(44)

©SAP AG 2005

Detailed Content

Functional Scope

(45)

©SAP AG 2005

System Monitoring – Detailed Content

Content for display and managing of alert situations

System Monitoring

All CCMS/RZ20 Data like Hardware, Databases, SAP Basis, SAP Internet

Transaction Server (SAP ITS), Internet Pricing & Configuration (SAP IPC),

Index Management Server (SAP IMS), SAP Business Connector (SAP BC),

SAP liveCache, In-Q-My Java Application Server

Partner Products, HTML-based components (generic)

Extension concept

Open interfaces for monitoring data providers and data consumers (e.g.

via SNMP traps)

(46)

©SAP AG 2005

Business Process Monitoring: Concept

Step 1

Identify core

business

processes

Step 2

Identify

process

steps and

interfaces

Step 3

Define

monitoring

objects

and tools

Step 4

Define error

handling

pro-cedures and

escalation

paths

Step 5

Define

monitoring

activities

Phases of a Software Implementation Project

Strategic

Framework

Technical

and Integration

Design

Technical and

Operations

Implementation

Cutover

and Start of

Production

Operations

and Continuous

Improvement

Define and

Create

a Monitoring

Concept

Implement the

Monitoring

Concept

Start

Monitoring

Change

Management

in Monitoring

Steps to Define and Create a

Business Process Monitoring Concept

The implementation of new software follows an implementation roadmap. In this roadmap the

definition and creation of a Business Process Monitoring concept is part of the implementation

section “Technical Integration and Design ” and consists of five steps. During these steps the

core business process is identified and specified. The monitoring objects are determined, and

the error handling procedures and monitoring activities are defined.

(47)

©SAP AG 2005

SAP Solution Manager 3.2: Functional Scope 1/3

Business Process Monitoring

types

and alert definition for:

(effective from SAP R/3 Release 4.0)

Background jobs

(running on SAP Systems with an R/3 Basis) for daily

and monthly jobs

Start delay

End delay

Out of time window

Maximum processing time

Dialog transaction performance monitoring (effective from SAP R/3 Release

4.6B)

of

Response, queue (wait), load and generation, DB, and

frontend (net) time per SAP Application Instance

Update errors

for transactions and programs

V1 update errors / V2 update errors

Application log

messages

Due list log

messages for deliveries and billings

Document volume

monitoring of

Inserts, updates, and deletes of any table at any time during a day

All alerts which are available or can be configured in the

CCMS Alert Monitor

Job cancellation

Wrong parallel processing

Job log messages

(48)

©SAP AG 2005

SAP Solution Manager 3.2: Functional Scope 2/3

New monitoring type “

Application Monitor

” providing Monitoring of

application-specific key figures

Monitoring of

due list logs

(SAP R/3 SD)

Monitoring of

MRP key figures

(SAP R/3 MM/PP)

User exits

that can be individually customized (ABAP)

Interface Monitoring for:

(effective from SAP R/3 Release 4.5B)

ALE / EDI (IDoc)

(effective from SAP R/3 Realease 4.6C)

Outbound

IDoc generated

IDoc ready for dispatch

IDoc in external system

IDoc dispatched

Error in IDoc interface

Error in External System

IDoc with delete flag

IDoc processing in target system

qRFC

Blocked queues

Errors in Queue Scheduler

tRFC (generic monitoring of tRFC tables)

Inbound

IDoc generated

IDoc transferred to application

IDoc transferred to dialog

Application document posted

Error in IDoc interface

Error in application

IDoc with delete flag

(49)

©SAP AG 2005

SAP Solution Manager 3.2: Functional Scope 3/3

Handling Features

Service Level (SL) Reporting

for Business Process Management

based on

Statistical performance data (EWA) for Service Level Agreements

Aggregated per day and business process, business process step,

monitoring type, and alert type

The number of green, yellow, and red alerts

The number of confirmed yellow and red alerts

Alerts can be directly confirmed (with user and time stamp)

Service Desk messages

can be manually created for single and

automatically created for any number of alerts

E-mails

(auto-reaction methods or workflow) can be automatically

(50)

©SAP AG 2005

Monitoring Configuration

•

Assign monitoring objects

to process steps and interfaces

•

Customize alerts per object

•

Use Best Practices for Business

Process Management to identify

monitoring objects.

Activate Monitoring

Process Definition in

•

Process Steps, Interfaces etc.

Setup of Business Process Monitoring in SAP Solution

Manager

Implementation

Project

Cancellation Alert for job

Create_Sales_Order

Manual entry

IDoc monitoring for

Type ORDERS

Application Log

monitoring for material

allocation error

messages

Performance monitoring

for transaction VL02N

Start Delay Alert for job

Create_Invoice

(51)

©SAP AG 2005

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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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. MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 in several other countries all over the world. 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.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP®_{product and is not intended to be binding upon SAP to any particular course of business, product}

strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.