SAP Solution Manager IT Service Management

Review of Critical Failure Areas in the IT Service

Management system
SAP Partner Service Delivery
March 2016
 DISCLAIMER

This material does not presume to document all potential failure areas in the IT Service Management
configuration by VARs. It serves as a guide for those areas which will be reviewed by the Auditor team
and those areas which have been observed as common mistakes in a VAR setup.

This guide does not serve as a tutorial or a configuration material and should not be viewed as such.
Features and screens taken reference SP08 and may change with other support package levels.

Where VARs encounter other issues other than those documented here, VARs are to be advised to take
the EGI for Application Incident Management ITSM for Service Providers or to seek Consulting advise.

Errors received with standard objects and procedures should be referred to SAP Support.

2016 SAP SE or an SAP affiliate company. All rights reserved. For internal SAP and partner use only 2
 TRANSACTION: AISUSER
Lists all users that participate in the incident handling process. This
includes both VAR support staff and VAR customer users.

EXPECTATIONS
ALL maintenance customers should be defined in this table.
PCAs will validate that the column SAP Customer Numbers
have all indirect customers defined.
VARs allowing customers to log incidents should have defined
customer user ids (such as their customers S-user IDs) in the
User column.

This requirement is mandatory for the following scenarios:

VARs supporting SAP Business All-In-One and/or SAP HANA.
VARs using SAP Solution Manager Incident Management as its
primary incident management system.

VARs and customers (where allowed) should be able to interact and process
incidents in the SAP Solution Manager Incident Management

2016 SAP SE or an SAP affiliate company. All rights reserved. For internal SAP and partner use only 3
 SAP Solution Manager Incident Management should be set up to
forward Very High incidents to SAP beyond office hours.

TRANSACTION: BP
Lists defined business partners in CRM (which is
used by ITSM). It is expected that all customers are
defined with a specific business partner number.

EXPECTATIONS
Support business hours should be documented
for every customer.
It is a failure criteria to have no support hours
defined for each customer where VAR relies on
SAP for delivering support beyond its office
times. For such situations, Very High incidents
posted outside office hours will not get
forwarded to SAP.

2016 SAP SE or an SAP affiliate company. All rights reserved. For internal SAP and partner use only 4
 TRANSACTION: SU01
Maintain user authorizations that define access and
capabilities by the user in the SAP system.

EXPECTATIONS
The Key User role should be maintained for all
customer user ids. It is strictly not advised to use
the Processor role for this purpose.
Customer users should not be given the
SAP_ALL profile.

Correct Key User role should be used and

no SAP_ALL authorization should be given
to customers.

2016 SAP SE or an SAP affiliate company. All rights reserved. For internal SAP and partner use only 5
 The following topics will require the Application
Incident Management Configuration Guide for
VAR IT Service Management.
Please reference the following page:

https://support.sap.com/solution-manager.html --
>SAP Solution Manager for Partners Service
Providers Solution Manager Setup Setup
Documents Administrator SAP Solution
Manager 7.1 VAR Config Guide

2016 SAP SE or an SAP affiliate company. All rights reserved. For internal SAP and partner use only 6
 CUSTOMER USER MANUAL (1)
This document is submitted as part of the checklist requirements and is
reviewed by the PCA to determine usage procedures by customer users.

Incorrect Incident Posting Procedure

The Create Incident menu should not be visible for customers to use.

Corrective Action
Follow instructions from 7.18 of the ITSM Service Provider Configuration
Manual with the following changes:
In point 1, Use business role SOLMANREQU instead of SOLMANPRO.
In point 5, instead of the instruction to Select and mark the specific
group id use Select and unmark group id SM-CREATE

The Create Incident menu from the left navigational panel
should not be visible or used for incident posting by customers.

2016 SAP SE or an SAP affiliate company. All rights reserved. For internal SAP and partner use only 7
 CUSTOMER USER MANUAL (2)
This document is submitted as part of the checklist
requirements and is reviewed by the PCA to
determine usage procedures by customer users.

Incorrect Incident Posting Procedure

The Installed Base Component field should not be

accessible or usable by customers. To select the

system where the error has occurred, customers
should use the field Configuration Item.

Corrective Action
Follow instructions from 7.17 of the ITSM Service
Provider Configuration Manual .

The Installed Base Component field should be a Display Only field and
is shown to be greyed out during incident posting.

2016 SAP SE or an SAP affiliate company. All rights reserved. For internal SAP and partner use only 8
Thank You!
 2016 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.

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. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional
trademark information and notices.

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 SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated
companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be
changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties
that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking
statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

2016 SAP SE or an SAP affiliate company. All rights reserved. For internal SAP and partner use only 10
 2016 SAP SE oder ein SAP-Konzernunternehmen.
Alle Rechte vorbehalten.

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die
ausdrckliche schriftliche Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet.

SAP und andere in diesem Dokument erwhnte Produkte und Dienstleistungen von SAP sowie die dazugehrigen Logos sind Marken oder
eingetragene Marken der SAP SE (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Lndern weltweit.
Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://global.sap.com/corporate-de/legal/copyright/index.epx.

Die von SAP SE oder deren Vertriebsfirmen angebotenen Softwareprodukte knnen Softwarekomponenten auch anderer Softwarehersteller
enthalten.

Produkte knnen lnderspezifische Unterschiede aufweisen.

Die vorliegenden Unterlagen werden von der SAP SE oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschlielich zu Informations-
zwecken. Die SAP SE oder ihre Konzernunternehmen bernehmen keinerlei Haftung oder Gewhrleistung fr Fehler oder Unvollstndigkeiten in
dieser Publikation. Die SAP SE oder ein SAP-Konzernunternehmen steht lediglich fr Produkte und Dienstleistungen nach der Magabe ein, die in der
Vereinbarung ber die jeweiligen Produkte und Dienstleistungen ausdrcklich geregelt ist. Keine der hierin enthaltenen Informationen ist als
zustzliche Garantie zu interpretieren.

Insbesondere sind die SAP SE oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehrigen Prsentation
dargestellte Geschftsablufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu verffentlichen. Diese Publikation oder
eine zugehrige Prsentation, die Strategie und etwaige knftige Entwicklungen, Produkte und/oder Plattformen der SAP SE oder ihrer Konzern-
unternehmen knnen von der SAP SE oder ihren Konzernunternehmen jederzeit und ohne Angabe von Grnden unangekndigt gendert werden.
Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von
Material, Code oder Funktionen dar. Smtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die
die tatschlichen Ergebnisse von den Erwartungen abweichen knnen. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder,
zu dem sie gettigt wurden. Dem Leser wird empfohlen, diesen Aussagen kein bertriebenes Vertrauen zu schenken und sich bei
Kaufentscheidungen nicht auf sie zu sttzen.

2016 SAP SE or an SAP affiliate company. All rights reserved. For internal SAP and partner use only 11