Side Effect Report Guide

Side-Effect-Report Guide

Last update: May 2010

Target Groups and Objectives

Objectives

At the end of this presentation, you will be able to:

Describe how a side effect report can be requested

Explain the side effect report content

Target Groups

This presentation is relevant to :

SAP Customers

SAP Partners

Other interested parties

© SAP 2009 / Side Effect Report Guide /

Side Effect Report

This report can be requested at

SAP Service Market Place (SAP SMP)

SAP Solution Manager – Maintenance Optimizer (MOpz)

It can be requested for

one single support package (SP)

a user defined list of support packages of one or multiple software component

versions

all support packages required to implement a SP stack

This report is available for ABAP support packages, only.


A side effect report is a list of solution notes, where the corresponding

causing notes are part of the support package(s) a customer plans to

implement.

Side Effect Report

Example

Level 1

Level 2

Level 3


With implementation

of these SPs …

.. a new error caused by this note

(as part of the mentioned SP)

will be introduced and …

… a solution is already known

by SAP, but not part of the

Support package queue.

What to do with the Side Effect Report?

The report could be printed. Recommendation is to download the report and check

which solution notes are relevant for the specific system.

Quick access to the notes in SAP SMP is available with a click on the note number

in the report.

All marked notes can be downloaded with SAP Download Manager.


Big or Small Input Queue?

Is there a difference of

multiple side effect report requests with few number of support packages and

one side effect report request which contains all support packages together?

If more support packages are selected, the report can be shorter. All

solution notes which are identified as part of the side effect report request

input queue will not appear on the result list! These solution notes will be

implemented with the support packages. The report shows the solution

notes which might be relevant for customers as well.


Request a side effect report with all support packages you plan to implement.

(e.g. SP stack)

How to Request a Side Effect Report for a

Single Support Package

At SAP SMP press the side-effect-report button next to the support package.


How to Request a Side Effect Report for a List

of Support Packages (I)

At SAP SMP, select Quick link /side-effects

http://service.sap.com/side-effects





How to Request a Side Effect Report for a List

of Support Packages (II)

Customers are able to define an individual support package queue, based on

system data maintained in CSS:



Complete SP Stack Implementation (I)

At http://service.sap.com/sp-stacksselect product version,

source stack and

target stack.

The report can be

requested in

step 3 of 3.


http://service.sap.com/sp-stacks




Complete SP Stack Implementation (II)

The real set of support packages a customer plans to implement during planned

maintenance is only known by SAP Solution Manager MOpz.


The side effect report request at SAP SMP for SP stacks is a static request based

on SP stack definitions.

To receive the best results based on current SP levels in the customer system

and selected target SP stack, a side effect report should always

be requested from MOpz maintenance transaction.

Lesson Summary

You should now be able to

Describe how a side effect report can be requested

Explain the side effect report content


Side Effect Report Guide

Documents

Transcript of Side Effect Report Guide